Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | STARTTLS enforcement for sslproto != "tls1". | Matthias Andree | 2020-01-04 | 1 | -1/+1 |
| | | | | | | | | | | Fetchmail < 6.4.2 used to only consider --sslproto=TLS1 as "mandatory STARTTLS" unless sslcertck or sslfingerprint were given, now all protocol versions will require STARTTLS. This did not matter in the default install because sslcertck defaults to on, but could permit fetchmail to continue with unencrypted connections if --nosslcertck was in use. | ||||
* | Minor Doxygen updates/fixes. | Matthias Andree | 2019-08-20 | 1 | -1/+1 |
| | | | | Reported by: Jens Schleusener (fossies.org) | ||||
* | TLS overhaul, bumping version to 6.4 | Matthias Andree | 2015-01-26 | 1 | -0/+37 |
Removes SSLv2, enables TLSv1.1 and v1.2 more easily, permits SSLv3 (only if specified) and newer TLSv1.1+ for STLS/STARTTLS. Only negotiates TLSv1 and newer by default, SSLv3 must now be specified explicitly, as a consequence of the POODLE attack. This is meant to be a minimally upgraded version, and cannot be usefully done as a 6.3.X release. It is strongly recommended that users review their configuration - especially --sslproto - per instructions in the NEWS file and manual page. It has changed semantics and in many cases --sslproto auto or perhaps --sslproto tls1.2+ should be used now. |