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.

Changes between Version 23 and Version 24 of CertMgr/ToDo


Ignore:
Timestamp:
Jul 13, 2007, 8:52:18 AM (17 years ago)
Author:
wehlhard
Comment:

up todo

Legend:

Unmodified
Added
Removed
Modified
  • CertMgr/ToDo

    v23 v24  
    2424  * Talking to nosnilmot suggests that this ought to just be removed outright (24 May)
    2525 * Figure out libNSS everything. (25 May)
     26  * http://lxr.mozilla.org/mozilla/ident?i=CERT_GetCertTimes
    2627 * Why am I getting single-byte serial numbers from servers? (25 May)
    27  * Work out how to use Glib functions for time checking on certificates. (29 May)
    2828 * Stall the timeouts on the TCP connection while waiting for user input on SSL? (29 May)
    2929 * Worry about ensuring that plugins don't kill in-use ciphers/certschemes when unloaded? (29 May)
     
    3535  * Implemented in f9e47ecff65cbcb1e87b8fedd271ec5b02123fcf, but may need testing (13 July)
    3636 * '''Refactoring.''' The certificate interface feels too complicated. (11 July)
    37  * Why won't gtkcertmgr.h get properly processed by "make docs"? (13 July)
     37 * activation/expiration should be made one function in the Scheme, as that's how NSS does it. (13 July)
    3838
    3939= Tasks done =
     
    4141 * GnuTLS and NSS should probably be configured to use g_malloc and g_free for paranoia's sake (1 June, 26 June)
    4242 * e408398aae606a1aafb857413db4fa9736e374ae should be disapproved. It is hacky and stupid (26 June, 7 July)
    43 
    44 = NSS Notes =
    45 http://lxr.mozilla.org/mozilla/ident?i=CERT_GetCertTimes
     43 * Why won't gtkcertmgr.h get properly processed by "make docs"? (13 July, 13 July)
     44  * sadrul is awesome. Typos are not.
     45 * Work out how to use Glib functions for time checking on certificates. (29 May, 13 July)
     46  * POSIX for the win.
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!