From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] apache-2.2.27 disable SSLCipherSuite LOW 40 56 bit
Date: Sun, 22 Jun 2014 09:55:40 +0100 [thread overview]
Message-ID: <201406220955.42494.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20140622012944.GA9332@syscon7>
[-- Attachment #1: Type: Text/Plain, Size: 1917 bytes --]
On Sunday 22 Jun 2014 02:29:44 Joseph wrote:
> Before upgrading to apache 2.2.27 I had this line in httpd.conf
> SSLProtocol -ALL +SSLv3 +TLSv1 +TLSv1.2
> SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:!EXPORT
>
> and I was getting "A-" rating from: www.ssllabs.com
>
> Now after upgrading to apache-2.2.27 I'm getting "C" because of weak Cipher
> Strength inclusion:
>
> TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x3) WEAK 40
> TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x6) WEAK 40
> TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x8) WEAK 40
> TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x14) DH 512 bits (p: 64, g: 1,
> Ys: 64) FS WEAK 40 TLS_RSA_WITH_DES_CBC_SHA (0x9) WEAK 56
> TLS_DHE_RSA_WITH_DES_CBC_SHA (0x15) DH 1024 bits (p: 128, g: 1, Ys: 128)
> FS WEAK 56
>
> How to get rid of it? I've tired setting in 00_default_ssl_vhost.conf
>
> SSLProtocol all -SSLv2 -SSLv3
It should be better to set -ALL to disable all protocols and then explicitly
enable only the protocols that you want to trust as secure, e.g. +TLSv1.2
> SSLCompression Off
> SSLCipherSuite "EECDH+AESGCM EDH+AESGCM EECDH -RC4 EDH -CAMELLIA -SEED
> !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS !RC4"
This leaves the anonymous DH enabled which will give you a poor rating.
> or
> SSLProtocol -ALL +SSLv3 +TLSv1 +TLSv1.2
> SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:!LOW:!SSLv2:!EXPORT
This enables RC4 which may give you a poor rating - not sure. Better you move
it down the list so that more secure ciphers are tried first.
> nothing helps, I'm still getting "C" because of weak Cipher Strength
> inclusion.
This is because you inadvertently allow weak ciphers in your directives above.
Try running openssl ciphers -v <string> to see what your directives allow and
in what order. Then modify them accordingly.
HTH.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-06-22 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 1:29 [gentoo-user] apache-2.2.27 disable SSLCipherSuite LOW 40 56 bit Joseph
2014-06-22 8:55 ` Mick [this message]
2014-06-22 16:59 ` Joseph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201406220955.42494.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox