README: Clarify that OpenSSL is not required for ECDHE

This commit is contained in:
Aaron Jones 2016-08-15 10:53:23 +00:00
parent e5afd80775
commit 897c10749d
No known key found for this signature in database
GPG key ID: EC6F86EE9CD840B5

View file

@ -16,18 +16,18 @@ used with an IRCv3-capable services implementation such as [Atheme][atheme] or [
* For SSL/TLS client and server connections, one of: * For SSL/TLS client and server connections, one of:
* OpenSSL 1.0 or newer * OpenSSL 1.0.0 or newer (--enable-openssl)
* LibreSSL * LibreSSL (--enable-openssl)
* mbedTLS * mbedTLS (--enable-mbedtls)
* GnuTLS * GnuTLS (--enable-gnutls)
* For certificate-based oper CHALLENGE, OpenSSL 1.0 or newer. * For certificate-based oper CHALLENGE, OpenSSL 1.0.0 or newer.
(Using CHALLENGE is not recommended for new deployments, so if you want to use a different TLS library, (Using CHALLENGE is not recommended for new deployments, so if you want to use a different TLS library,
feel free.) feel free.)
* For ECDHE, OpenSSL 1.0.0 or newer is required. RHEL/Fedora and derivatives like CentOS * For ECDHE under OpenSSL, on Solaris and RHEL/Fedora (and its derivatives such as CentOS) you will
will need to compile OpenSSL from source, as ECC/ECDHE-functionality is removed from need to compile your own OpenSSL on these systems, as they have removed support for ECC/ECDHE.
the OpenSSL package in these distributions. Alternatively, consider using another library (see above).
# tips # tips