Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Aug 13, 2007, 8:35:12 PM (16 years ago)
- Author:
-
wehlhard
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v31
|
v32
|
|
21 | 21 | * Look at how the SILC prpl does its key management, especially the organization of the API used to check certs and interact with the user to verify them. |
22 | 22 | * Add some way of passing useful error messages back up out of the SSL interface (23 May) |
23 | | * Fix purple_ssl_init in sslconn.c; it doesn't do anything (23 May) |
24 | | * Talking to nosnilmot suggests that this ought to just be removed outright (24 May) |
25 | 23 | * Figure out libNSS everything. (25 May) |
26 | 24 | * http://lxr.mozilla.org/mozilla/ident?i=CERT_GetCertTimes |
… |
… |
|
30 | 28 | * Adium uses neither GnuTLS nor NSS. Look into extending the OpenSSL plugin (26 June) |
31 | 29 | * Guarantee that purple_certificate_verify will '''not''' fire its callback until the next return to mainloop. sadrul says to do this with g_timeout_add (June 28) |
32 | | * Change the things that purple_certificate_verify does such that it is easy for one verification request to make another. This will involve making a "copy" operator for certificates. (7 July) |
33 | 30 | * Disapprove 42fb4d80947518f87ddcaf43bf2675d8496698de (7 July) |
34 | 31 | * '''Refactoring.''' The certificate interface feels too complicated. (11 July) |
… |
… |
|
51 | 48 | * Implemented in f9e47ecff65cbcb1e87b8fedd271ec5b02123fcf for GnuTLS (13 July) |
52 | 49 | * NSS does reference counting already (13 Aug) |
| 50 | * Change the things that purple_certificate_verify does such that it is easy for one verification request to make another. This will involve making a "copy" operator for certificates. (7 July, 13 Aug) |
| 51 | * Fix purple_ssl_init in sslconn.c; it doesn't do anything (23 May, 13 Aug) |
| 52 | * Side effects of lazy init were biting me. It now does something. (13 Aug) |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!