6e61939382
internally, with code provided by sslgen.c. All SSL-layer-specific code is then written in ssluse.c (for OpenSSL) and gtls.c (for GnuTLS). As far as possible, internals should not need to know what SSL layer that is in use. Building with GnuTLS currently makes two test cases fail. TODO.gnutls contains a few known outstanding issues for the GnuTLS support. GnuTLS support is enabled with configure --with-gnutls
22 lines
793 B
Plaintext
22 lines
793 B
Plaintext
Things to fix for the GnuTLS support
|
|
====================================
|
|
|
|
* set LD_LIBRARY_PATH in configure when the GnuTLS lib was found, to fix link
|
|
problems that othwerwise might happen within configure. Compare with OpenSSL
|
|
stuff.
|
|
|
|
* make the configure --with-ssl option first check for OpenSSL and then for
|
|
GnuTLS if OpenSSL wasn't detected.
|
|
|
|
* Get NTLM working using the functions provided by libgcrypt, since GnuTLS
|
|
already depends on that to function. Not strictly SSL/TLS related, but
|
|
hey... Another option is to get available DES and MD4 source code from the
|
|
cryptopp library. They are fine license-wise, but are C++.
|
|
|
|
* SSL engine stuff?
|
|
|
|
SRP for TLS
|
|
|
|
* Work out a common method with Peter Sylvester's OpenSSL-patch for SRP
|
|
on the TLS to provide name and password
|