Hi Simon & Matthias
Thanks for your great work! We're currently testing the version from the
mercurial repository and it works so far without any issue (SUSE Linux
Enterprise Server 11SP4). As it seems to be very stable (after some tests)
we deployed it to our productive environment with a current workload of
about 5000 concurrent user to further test the stability. We'll still keep
an eye on it...
this short series allows the configuration of more SSL/TLS protocol
options at run time.
* Provides options to set the minimum and maximum SSL/TLS protocol version.
The new default is that SSLv3 and earlier are disabled.
SSLv2 may not be enabled.
* Provides an options to allow compression.
The new default is that compression is disabled.
* Provides an option to disable server cipher preference.
The new default is to set server cipher preference.
Thanks to Matthias Hunstock for his patch which provided the basis for this
Review and testing would be appreciated.
Changes since RFT (v1):
* Enforce SSLv3 minimum version
* Add compression and server cipher preference patches
did you have any success disabling SSLv3? I would like to disable any
old ciphers and turn on Forward Secrecy. Do you have experience with
this and perdition?
From: Xavier Garcia <xavi.garcia <at> gmail.com>
Subject: Re: Disabling SSLv3
Date: 2014-10-31 13:31:23 GMT (43 weeks, 1 hour and 45 minutes ago)
AFAIK, this enables STARTTLS in the port instead of starting a
purely encrypted connection.
nc -vv imapproxy01i 993
Connection to imapproxy01i 993 port [tcp/imaps] succeeded!
* OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES
* MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE
* LOGIN-REFERRALS STARTTLS LOGINDISABLED] perdition ready on
* imapproxy01i 00028de7
I haven't tested but I think this may not change the list of
accepted cyphers. After reading the manual and some messages in
the list, it seems that all references to TLS in the
configuration are aiming at STARTTLS and the only way to change
the valid ciphers is with *ssl_listen_ciphers* and
*ssl_outgoing_ciphers*. Am I mistaken?
On Fri, Oct 31, 2014 at 02:10:42PM +0100, LE SAOUT Mael wrote:
> Hi all,
> I have to disable it in /etc/sysconfig/perdition :
> POP3S_FLAGS="--outgoing_port 110 --ssl_mode tls_listen,tls_listen_force"
> IMAP4S_FLAGS="--outgoing_port 143 --ssl_mode tls_listen,tls_listen_force"
> Hope it will help you.
> -----Message d'origine-----
> De?: perdition-users-bounces <at> vergenet.net [mailto:perdition-users-bounces <at> vergenet.net] De la
part de Xavier Garcia
> Envoy??: vendredi 31 octobre 2014 13:59
> ??: perdition-users <at> vergenet.net
> Objet?: [PERDITION-USERS] Disabling SSLv3
> Dear all,
> I am trying to disable SSLv3 on perdition 2.0-1.x86_64 It is running in a RHEL 6.5 clone and it was compiled
with the SPEC files.
> In theory, I should apply the following configuration but it also disables TLSv1 and TLSv1.1, being
TLSv1.2 still available.
> ssl_listen_ciphers "ALL:!SSLv2:!SSLv3"
> I don't know much about cryptography but I guess it makes sense because I obtain the same result in all my
boxes (RHEL 6.5 , Fedora and FreeBSD 10) when I execute:
> openssl ciphers -v 'ALL:!SSLv2:!SSLv3'
> What would be the best way to disable SSLv2 and SSLv3 for incoming and outgoing connections?
> Xavier Garcia
> Perdition-users mailing list
> Perdition-users <at> vergenet.net
Perdition-users mailing list
Perdition-users <at> vergenet.nethttp://lists.vergenet.net/listinfo/perdition-users