Tickets :: Comment on [#13730] Implementation of peer verification in TLS connections

* Your Email Address
* Spam protection	Enter the letters below: .__..__ . .. ..___ \| \|[ __\|\ \|\|__\|[__ \|__\|[_./\| \\|\| \|\|
Comment	> Horde does not verify the peer certificate during TLS handshake and > accepts all ciphers when acting as client. This is probably to enable > self-signed certificates. However, in an environment where a secure > connection matters this behavior is not acceptable. Therefore I added > the possibility to enable peer verification and cipher selection. > This options can be found in the openssl tab in horde's > configuration. If enabled, this options will be used by client.php to > verify the peer certificate during the TLS handshake. > > === Benefits and Limitations === > The main benefit is to enforce a secure connection between the server > running horde and the backend server. Other security meassurements > (e.g. fingerprint checking) provided by PHP are not part of this > implementation. > > === Regressions === > The patch was only checked with an IMAP server as backend. However, > the changes have no effect until the peer verification is > deliberately enabled. So, there should not be any regressions.
Attachment
Watch this ticket