generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

TODO: support DANE, we already support gnutls without gcrypt

Browse Source
This commit is contained in:
Daniel Stenberg 2012-08-07 14:48:34 +02:00
parent 382429e760
commit 013d043d22
1 changed files with 8 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/TODO
View File

@ -55,11 +55,11 @@
7.6 Provide callback for cert verification 7.6 Provide callback for cert verification
7.7 Support other SSL libraries 7.7 Support other SSL libraries
7.9 improve configure --with-ssl 7.9 improve configure --with-ssl
7.10 Support DANE
8. GnuTLS 8. GnuTLS
8.1 SSL engine stuff 8.1 SSL engine stuff
8.3 check connection 8.3 check connection
8.4 non-gcrypt
9. SMTP 9. SMTP
9.1 Specify the preferred authentication mechanism 9.1 Specify the preferred authentication mechanism
@ -355,6 +355,13 @@ to provide the data to send.
make the configure --with-ssl option first check for OpenSSL, then GnuTLS, make the configure --with-ssl option first check for OpenSSL, then GnuTLS,
then NSS... then NSS...
7.10 Support DANE
DNS-Based Authentication of Named Entities (DANE) is a way to provide SSL
keys and certs over DNS using DNSSEC as an alternative to the CA model.
http://www.rfc-editor.org/rfc/rfc6698.txt
8. GnuTLS 8. GnuTLS
8.1 SSL engine stuff 8.1 SSL engine stuff
@ -366,16 +373,6 @@ to provide the data to send.
Add a way to check if the connection seems to be alive, to correspond to the Add a way to check if the connection seems to be alive, to correspond to the
SSL_peak() way we use with OpenSSL. SSL_peak() way we use with OpenSSL.
8.4 non-gcrypt
libcurl assumes that there are gcrypt functions available when
GnuTLS is.
GnuTLS can be built to use libnettle instead as crypto library,
which breaks the previously mentioned assumption
The correct fix would be to detect which crypto layer that is in use and
adapt our code to use that instead of blindly assuming gcrypt.
9. SMTP 9. SMTP