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:
-
Jun 27, 2007, 12:31:09 AM (17 years ago)
- Author:
-
wehlhard
- Comment:
-
free preview buttons!
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v4
|
v5
|
|
2 | 2 | * Design issue: In my design, the Certificate struct has an ptr to a GnuTLS certificate structure to hold its internal data. This has the consequence that the SSL connection system and X.509 handling must both be provided by GnuTLS; if, say, SILC provides the X.509 handling, and GnuTLS the SSL connections, everything grinds to a gruesome segfaulty halt. |
3 | 3 | |
4 | | Should I address this? The only workaround I can think of is to keep a pointer to the PEM-formatted certificate in the Certificate struct instead, but that will require any consumers |
| 4 | Should I address this? The only workaround I can think of is to keep a pointer to the PEM-formatted certificate in the Certificate struct instead, but that will require any consumers of the Certificate to have PEM encoding/decoding and constantly decode it from PEM for every use. (June 19) |
| 5 | |
5 | 6 | * How to ensure that VerificationRequests get properly trashed in unusual conditions (such as canceling an SSL connection)? (June 26) |
6 | | of the Certificate to have PEM encoding/decoding and constantly decode it from PEM for every use. (June 19) |
7 | 7 | = Resolved Issues = |
8 | 8 | * It looks like PKCS12 (the certificate import/export format) is supported by both libNSS and GnuTLS. |
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!