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 18, 2007, 3:23:04 AM (16 years ago)
- Author:
-
wehlhard
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v34
|
v35
|
|
| 8 | 8 | * Jabber.org presents a cert with a CN of "*.jabber.org". How to check this? (26 June) |
| 9 | 9 | * Update: This is *almost* valid. "foo.jabber.org" is valid with this certificate, but not "jabber.org" itself! (8 July) |
| | 10 | * The certificate has jabber.org as an alternative name in an extension. GnuTLS should be dealing with this automatically. We'll see what NSS does (17 Aug) |
| 10 | 11 | |
| 11 | 12 | * #1947 |
| … |
… |
|
| 37 | 38 | * '''Crasher:''' Click "delete" twice, then hit "yes" to both dialogs. (13 Aug) |
| 38 | 39 | * Certificates require some kind of metadata system. For example, it would be useful to alert the user when a cached certificate has expired, but, should he dismiss the request and opt not to be prompted again, to respect his wishes and not bother him. (14 Aug) |
| | 40 | * Provide a way to specify "do not use this certificate, even if it is properly signed" option through the certmgr GUI. The backend (by cert hash, the full cert, etc.) isn't all that important. GUI might be a checkbox in the certlist, or an extra tab. (17 Aug) |
| 39 | 41 | |
| 40 | 42 | = Tasks done = |
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!
