Changes between Version 22 and Version 23 of CertMgr

Timestamp:

May 30, 2007, 6:26:13 AM (17 years ago)

Author:

wehlhard

Comment:

--

CertMgr

@@ -26 +26 @@
 TODO: Go through the full "create an SSL connection" process and figure out how everything fits in.
 
+== Key Store ==
+The API for this hasn't been decided yet. However, the organization will look something like this:
+~/.purple/certificates/cert_scheme_name/cert_unique_id(.pem?)
+So an example X.509 certificate might be stored as:
+~/.purple/certificates/x509/gmail_com_1234567890abcdef1234567890abcdef.pem
+Some metadata may be necessary for each certificate.
+
+== Miscellaneous API changes ==
+* Jabber (and possibly other protocols) use purple_ssl_connect_fd to create SSL connections, throwing out possibly important data about the other end of the connection (hostname, port number) in the process. In the interests of keeping this data intact, I propose adding a purple_ssl_connect_proxyconn that will create an SSL connection around a previously existing ProxyConnection instead of ripping out its file descriptor and starting anew.
 
 = Issues =
@@ -50 +59 @@
 
 = Status =
+== 29 May 2007 ==
+With some prodding from Ethan, a lot of stuff came together for me design-wise today. I got a substantial part of the API changes laid out.
 == 25 May 2007 ==
 Divergence point reached. With the addition of purple_base16_encode_chunked, my changes will force at least a minor version increment.