You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Christopher Schultz <ch...@christopherschultz.net> on 2014/04/17 18:27:37 UTC
[users@httpd] Enabling ECDHE ciphers
All,
I'm trying to enable (and prefer!) ECDHE ciphers for clients that can
support them. I've done the obvious:
SSLHonorCipherOrder Yes
SSLProtocol ALL -SSLv2
SSLCipherSuite ECDHE:ECDH:..[other stuff]
I have confirmed that, when running "openssl ciphers [stuff above]" that
I get ECDHE ciphers listed at the top of the list. I'm running OpenSSL
1.0.1g-FIPS so that shouldn't be a problem.
Both my browser and Qualys's SSL tester don't seem to be able to use
those ciphers. Is it because I haven't done run "openssl ecparam"? I
haven't seen this shown as a requirement anywhere for enabling ECDHE (or
ECDH) ciphers anywhere online, though it makes sense that I'd have to do
something like that.
Or is it because I have "SSLProtocols ALL -SSLv2", which prefers SSLv3,
then TLSv1, then TLSv1.1, etc. instead of having them in the opposite
order? I tried "SSLProtocols TLSv1.2 TLSv1.1 TLSv1 SSLv3 -SSLv2" but I
get an error saying that "TLSv1.2 is unrecognized".
I'm running httpd 2.2.23 on Amazon Linux. I read in the comments for
mos_ssl that httpd 2.2.24 is required for "TLSv1.2" to be specified
directly. Is that accurate? I can see in my Qualys test that TLS 1.2 can
be used by some of the "simulated clients", so I suspect that it is in
fact available -- perhaps just not preferred?
Any help would be appreciated.
Thanks,
-chris
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Igor Cicimov <ic...@gmail.com>.
On Fri, Apr 18, 2014 at 2:27 AM, Christopher Schultz <
chris@christopherschultz.net> wrote:
>
> I'm running httpd 2.2.23 on Amazon Linux. I read in the comments for
> mos_ssl that httpd 2.2.24 is required for "TLSv1.2" to be specified
> directly. Is that accurate? I can see in my Qualys test that TLS 1.2 can
> be used by some of the "simulated clients", so I suspect that it is in
> fact available -- perhaps just not preferred?
>
> As far as I know it is the difference in the mod_ssl support.
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Hanno,
On 4/17/14, 12:29 PM, Hanno Böck wrote:
> On Thu, 17 Apr 2014 12:27:37 -0400
> Christopher Schultz <ch...@christopherschultz.net> wrote:
>
>> I'm trying to enable (and prefer!) ECDHE ciphers for clients that can
>> support them. I've done the obvious:
> [...]
>> I'm running httpd 2.2.23
>
> That's your problem. Get rid of that old cruft. You'll need apache 2.4
> (for that and for many other improvements regarding ssl encryption).
What is it about httpd 2.4 that enables a particular cipher? I figured
that if OpenSSL supported it, httpd would as well. Is there something
about ECDHE that requires more plumbing on the httpd side?
Thanks,
-chris
Re: [users@httpd] Enabling ECDHE ciphers
Posted by "Brett @Google" <br...@gmail.com>.
*16-November-2013 Changes with Apache 2.2.26 (legacy)*
ASF changes:
*) mod_ssl: enable support for ECC keys and ECDH ciphers. Tested against
OpenSSL 1.0.0b3. [Vipul Gupta, Sander Temme, Stefan Fritsch]
So you need something at least 2.2.26 (the ECDH changes were
backported from 2.4)
We run 2.2.27 with 1.0.1g and it tests as an A on Qualsys (side effect
is you get Perfect Forward Security, except for some older IE
versions).
Cheers
Brett
On Fri, Apr 18, 2014 at 10:56 AM, Igor Cicimov <ic...@gmail.com> wrote:
>
> On 18/04/2014 2:30 AM, "Hanno Böck" <ha...@hboeck.de> wrote:
> >
> > On Thu, 17 Apr 2014 12:27:37 -0400
> > Christopher Schultz <ch...@christopherschultz.net> wrote:
> >
> > > I'm trying to enable (and prefer!) ECDHE ciphers for clients that can
> > > support them. I've done the obvious:
> > [...]
> > > I'm running httpd 2.2.23
> >
> > That's your problem. Get rid of that old cruft. You'll need apache 2.4
> > (for that and for many other improvements regarding ssl encryption).
> >
> No you don't i have 2.2 with latest openssl-1.0.1g on all my servers and
> TLSv1.2 and ECDHE ciphers are supported.
>
> > --
> > Hanno Böck
> > http://hboeck.de/
> >
> > mail/jabber: hanno@hboeck.de
> > GPG: BBB51E42
>
--
Whenever you find yourself on the side of the majority, it is time to pause
and reflect.
- Mark Twain
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Christopher Schultz <ch...@christopherschultz.net>.
J.Lance,
On 4/18/14, 2:55 PM, J.Lance Wilkinson wrote:
> Christopher Schultz wrote:
> ...snip...
>>
>> I don't get it. Both setups (2.2.26 and 2.4.9) have 1.0.1.e and have an
>> update available to 1.0.1g (I haven't read the changelogs but I'll bet
>> the difference is mostly the version-bump since everyone is paranoid
>> about 1.0.1e, now). I'll see if that changes anything.
>
> Chris,
> What OS are you running? RHEL6?
Something like that. It's "Amazon Linux" which is RHEL-compatible.
> If so, then you actually do have the patched version EQUIVALENT to 1.0.1g,
> so my local Linux guru tells me.
>
> On RHEL6, I get:
> % openssl version
> OpenSSL 1.0.1e-fips 11 Feb 2013
>
> BUT, I also get:
> ~% rpm -q openssl
> openssl-1.0.1e-16.el6_5.7.x86_64
>
>
> RedHat, he tells me, does not distribute the new version but actually
> weng back and applied the relevant patches TO THEIR DISTRIBUTED
> VERSION. Note the -16.
> That's the indicator.
Yes, I'm aware. Amazon released another update that brings the version
explicitly up to 1.0.1g. I am aware that I saw safe from Heartbleed even
with the older version.
> It seems that RedHat thinks they know better than we.
The difference is that the patched 1.0.1e had only the security patch
for Heartbleed. I suspect that the difference between 1.0.1e and 1.0.1g
directly from OpenSSL includes more changes than just the Heartbleed
patch. This is how most distros work: they back-port only the patches
that are appropriate instead of always including version.current for
their updates.
Anyhow, it seems you've strayed off-topic because this isn't about which
is more appropriate -- 1.0.1e or 1.0.1g... it's about why I can't seem
to get httpd 2.2.26 to use ECDHE ciphers. I suspect it has something to
do with Amazon's build process even though the libraries are
dynamically-linked. Perhaps httpd was built against 1.0.0 so does not
include certain capabilities even though 1.0.1g is available at run-time.
-chris
Re: [users@httpd] Enabling ECDHE ciphers
Posted by "J.Lance Wilkinson" <jl...@psu.edu>.
Christopher Schultz wrote:
...snip...
>
> I don't get it. Both setups (2.2.26 and 2.4.9) have 1.0.1.e and have an
> update available to 1.0.1g (I haven't read the changelogs but I'll bet
> the difference is mostly the version-bump since everyone is paranoid
> about 1.0.1e, now). I'll see if that changes anything.
Chris,
What OS are you running? RHEL6?
If so, then you actually do have the patched version EQUIVALENT to 1.0.1g,
so my local Linux guru tells me.
On RHEL6, I get:
% openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
BUT, I also get:
~% rpm -q openssl
openssl-1.0.1e-16.el6_5.7.x86_64
RedHat, he tells me, does not distribute the new version but actually weng back
and applied the relevant patches TO THEIR DISTRIBUTED VERSION. Note the -16.
That's the indicator.
It seems that RedHat thinks they know better than we.
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
Systems Design Specialist - Lead Phone: (814) 865-4870
Information Technology Services FAX: (814) 863-3560
Penn State University
Digital Library Technologies, E3 Paterno Library, University Park, PA 16802
http://ucs.psu.edu/home/jlw12@psu.edu?fmt=freebusy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Christopher Schultz <ch...@christopherschultz.net>.
John,
On 4/18/14, 1:16 PM, John Iliffe wrote:
> Further to my previous post, the log reports:
>
> [Sun Apr 13 03:20:08.591247 2014] [mpm_event:notice] [pid 11737:tid
> 140478837470976] AH00489: Apache/2.4.9 (Unix) OpenSSL/1.0.1g configured --
> resuming normal operations
> [Sun Apr 13 03:20:08.591283 2014] [core:notice] [pid 11737:tid
> 140478837470976] AH00094: Command line: '/usr/apache-2.4.9/bin/httpd'
>
> BUT the libssl in use, and resulting from installing OpenSSL-1.0.1g, is
> libssl-1.0.0
My setup is a little different:
$ httpd -v
Server version: Apache/2.2.23 (Unix)
Server built: Oct 21 2012 20:35:47
$ ldd /usr/sbin/httpd
linux-gate.so.1 => (0xb7761000)
libm.so.6 => /lib/i686/nosegneg/libm.so.6 (0xb76c3000)
libpcre.so.0 => /lib/libpcre.so.0 (0xb7668000)
libselinux.so.1 => /lib/libselinux.so.1 (0xb7649000)
libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0xb7625000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb75f6000)
libexpat.so.1 => /lib/libexpat.so.1 (0xb75d0000)
libdb-4.7.so => /lib/libdb-4.7.so (0xb745e000)
libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0xb7430000)
libpthread.so.0 => /lib/i686/nosegneg/libpthread.so.0 (0xb7415000)
libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb726f000)
/lib/ld-linux.so.2 (0xb7762000)
libdl.so.2 => /lib/libdl.so.2 (0xb726a000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb7265000)
libfreebl3.so => /lib/libfreebl3.so (0xb7206000)
$ ldd /usr/lib/libapr-1.so.0
linux-gate.so.1 => (0xb779a000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb7760000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7731000)
libpthread.so.0 => /lib/i686/nosegneg/libpthread.so.0 (0xb7717000)
libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb7570000)
/lib/ld-linux.so.2 (0xb779b000)
libfreebl3.so => /lib/libfreebl3.so (0xb7511000)
libdl.so.2 => /lib/libdl.so.2 (0xb750c000)
$ ldd /usr/lib/httpd/modules/mod_ssl.so
linux-gate.so.1 => (0xb76f3000)
libssl.so.10 => /usr/lib/libssl.so.10 (0xb765d000)
libcrypto.so.10 => /lib/libcrypto.so.10 (0xb74a6000)
libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb7300000)
libgssapi_krb5.so.2 => /lib/libgssapi_krb5.so.2 (0xb72c2000)
libkrb5.so.3 => /lib/libkrb5.so.3 (0xb71f3000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0xb71ef000)
libk5crypto.so.3 => /lib/libk5crypto.so.3 (0xb71c4000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb71ad000)
libdl.so.2 => /lib/libdl.so.2 (0xb71a8000)
libz.so.1 => /lib/libz.so.1 (0xb7192000)
/lib/ld-linux.so.2 (0xb76f4000)
libkrb5support.so.0 => /lib/libkrb5support.so.0 (0xb7187000)
libkeyutils.so.1 => /lib/libkeyutils.so.1 (0xb7183000)
libpthread.so.0 => /lib/i686/nosegneg/libpthread.so.0 (0xb7169000)
libselinux.so.1 => /lib/libselinux.so.1 (0xb714a000)
$ ls -l /usr/lib/libssl.so.10
lrwxrwxrwx 1 root root 16 Apr 8 15:38 /usr/lib/libssl.so.10 ->
libssl.so.1.0.1e
$ openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
$ sudo grep "resuming" /var/log/httpd/error_log
[Fri Apr 18 03:21:02 2014] [notice] Apache/2.2.23 (Unix) DAV/2
mod_jk/1.2.37 PHP/5.3.28 mod_ssl/2.2.23 OpenSSL/1.0.0-fips configured --
resuming normal operations
So httpd is dynamically-linked to OpenSSL 1.0.1e (really 1.0.1g, with a
very important patch ;) and yet it reports OpenSSL 1.0.0 on startup.
I don't get it. Both setups (2.2.26 and 2.4.9) have 1.0.1.e and have an
update available to 1.0.1g (I haven't read the changelogs but I'll bet
the difference is mostly the version-bump since everyone is paranoid
about 1.0.1e, now). I'll see if that changes anything.
-chris
Re: [users@httpd] Enabling ECDHE ciphers
Posted by John Iliffe <jo...@iliffe.ca>.
Further to my previous post, the log reports:
[Sun Apr 13 03:20:08.591247 2014] [mpm_event:notice] [pid 11737:tid
140478837470976] AH00489: Apache/2.4.9 (Unix) OpenSSL/1.0.1g configured --
resuming normal operations
[Sun Apr 13 03:20:08.591283 2014] [core:notice] [pid 11737:tid
140478837470976] AH00094: Command line: '/usr/apache-2.4.9/bin/httpd'
BUT the libssl in use, and resulting from installing OpenSSL-1.0.1g, is
libssl-1.0.0
John
==========================================
On Friday 18 April 2014 13:08:12 John Iliffe wrote:
> Re the version of OpenSSL, I reported this last week to this list.
>
> Seems that OpenSSL-1.0.1g is linked to libssl-1.0.0, not the usual
> libssl-1.x.x format.
>
> Probably a make file error, but it really seems to be 1.0.1g.
>
> John
> =================================
>
> On Friday 18 April 2014 12:14:32 Christopher Schultz wrote:
> > Igor,
> >
> > On 4/17/14, 8:56 PM, Igor Cicimov wrote:
> > > On 18/04/2014 2:30 AM, "Hanno Böck" <hanno@hboeck.de
> > >
> > > <ma...@hboeck.de>> wrote:
> > >> On Thu, 17 Apr 2014 12:27:37 -0400
> > >> Christopher Schultz <chris@christopherschultz.net
> > >
> > > <ma...@christopherschultz.net>> wrote:
> > >> > I'm trying to enable (and prefer!) ECDHE ciphers for clients that
> > >> > can
> > >>
> > >> > support them. I've done the obvious:
> > >> [...]
> > >>
> > >> > I'm running httpd 2.2.23
> > >>
> > >> That's your problem. Get rid of that old cruft. You'll need apache
> > >> 2.4 (for that and for many other improvements regarding ssl
> > >> encryption).
> > >
> > > No you don't i have 2.2 with latest openssl-1.0.1g on all my servers
> > > and TLSv1.2 and ECDHE ciphers are supported.
> >
> > I checked, and even though I have the OpenSSL 1.0.1g package
> > installed, it appears that httpd was compiled against OpenSSL 1.0.0.
> > When I look at the start up log, it says:
> >
> > [Mon Apr 14 15:49:34 2014] [notice] Apache/2.2.23 (Unix) DAV/2
> > mod_jk/1.2.37 PHP/5.3.28 mod_ssl/2.2.23 OpenSSL/1.0.0-fips configured
> > -- resuming normal operations
> >
> > On another test server, I upgraded to the latest 2.2.x httpd I can get
> > from Amazon, which is 2.2.26. I re-started and still can't seem to use
> > the ECDHE algorithms.
> >
> > On that same (second) test server I upgraded to httpd 2.4.9. Here is
> > the startup log message there:
> >
> > [Fri Apr 18 15:53:26.330856 2014] [mpm_prefork:notice] [pid 15337]
> > AH00163: Apache/2.4.9 (Amazon) OpenSSL/1.0.1e-fips PHP/5.5.10
> > mod_jk/1.2.40 configured -- resuming normal operations
> >
> > I'm now able to use the ECDHE ciphers.
> >
> > Everything appears to be dynamically-linked, so I can't understand why
> > 2.2.x reports it's running with OpenSSL 1.0.0 when I clearly have
> > 1.0.1 installed. This is almost certainly an Amazon-Linux-related
> > thing if you were able to get ECDHE ciphers working on 2.2.x.
> >
> > I wonder, what does your startup string say about OpenSSL?
> >
> > The good news is that I really did only have to put it in my ciphers
> > list.
> >
> > Thanks,
> > -chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Enabling ECDHE ciphers
Posted by John Iliffe <jo...@iliffe.ca>.
Re the version of OpenSSL, I reported this last week to this list.
Seems that OpenSSL-1.0.1g is linked to libssl-1.0.0, not the usual
libssl-1.x.x format.
Probably a make file error, but it really seems to be 1.0.1g.
John
=================================
On Friday 18 April 2014 12:14:32 Christopher Schultz wrote:
> Igor,
>
> On 4/17/14, 8:56 PM, Igor Cicimov wrote:
> > On 18/04/2014 2:30 AM, "Hanno Böck" <hanno@hboeck.de
> >
> > <ma...@hboeck.de>> wrote:
> >> On Thu, 17 Apr 2014 12:27:37 -0400
> >> Christopher Schultz <chris@christopherschultz.net
> >
> > <ma...@christopherschultz.net>> wrote:
> >> > I'm trying to enable (and prefer!) ECDHE ciphers for clients that
> >> > can
> >>
> >> > support them. I've done the obvious:
> >> [...]
> >>
> >> > I'm running httpd 2.2.23
> >>
> >> That's your problem. Get rid of that old cruft. You'll need apache
> >> 2.4 (for that and for many other improvements regarding ssl
> >> encryption).
> >
> > No you don't i have 2.2 with latest openssl-1.0.1g on all my servers
> > and TLSv1.2 and ECDHE ciphers are supported.
>
> I checked, and even though I have the OpenSSL 1.0.1g package installed,
> it appears that httpd was compiled against OpenSSL 1.0.0. When I look at
> the start up log, it says:
>
> [Mon Apr 14 15:49:34 2014] [notice] Apache/2.2.23 (Unix) DAV/2
> mod_jk/1.2.37 PHP/5.3.28 mod_ssl/2.2.23 OpenSSL/1.0.0-fips configured --
> resuming normal operations
>
> On another test server, I upgraded to the latest 2.2.x httpd I can get
> from Amazon, which is 2.2.26. I re-started and still can't seem to use
> the ECDHE algorithms.
>
> On that same (second) test server I upgraded to httpd 2.4.9. Here is the
> startup log message there:
>
> [Fri Apr 18 15:53:26.330856 2014] [mpm_prefork:notice] [pid 15337]
> AH00163: Apache/2.4.9 (Amazon) OpenSSL/1.0.1e-fips PHP/5.5.10
> mod_jk/1.2.40 configured -- resuming normal operations
>
> I'm now able to use the ECDHE ciphers.
>
> Everything appears to be dynamically-linked, so I can't understand why
> 2.2.x reports it's running with OpenSSL 1.0.0 when I clearly have 1.0.1
> installed. This is almost certainly an Amazon-Linux-related thing if you
> were able to get ECDHE ciphers working on 2.2.x.
>
> I wonder, what does your startup string say about OpenSSL?
>
> The good news is that I really did only have to put it in my ciphers
> list.
>
> Thanks,
> -chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Igor,
On 4/17/14, 8:56 PM, Igor Cicimov wrote:
>
> On 18/04/2014 2:30 AM, "Hanno Böck" <hanno@hboeck.de
> <ma...@hboeck.de>> wrote:
>>
>> On Thu, 17 Apr 2014 12:27:37 -0400
>> Christopher Schultz <chris@christopherschultz.net
> <ma...@christopherschultz.net>> wrote:
>>
>> > I'm trying to enable (and prefer!) ECDHE ciphers for clients that can
>> > support them. I've done the obvious:
>> [...]
>> > I'm running httpd 2.2.23
>>
>> That's your problem. Get rid of that old cruft. You'll need apache 2.4
>> (for that and for many other improvements regarding ssl encryption).
>>
> No you don't i have 2.2 with latest openssl-1.0.1g on all my servers and
> TLSv1.2 and ECDHE ciphers are supported.
I checked, and even though I have the OpenSSL 1.0.1g package installed,
it appears that httpd was compiled against OpenSSL 1.0.0. When I look at
the start up log, it says:
[Mon Apr 14 15:49:34 2014] [notice] Apache/2.2.23 (Unix) DAV/2
mod_jk/1.2.37 PHP/5.3.28 mod_ssl/2.2.23 OpenSSL/1.0.0-fips configured --
resuming normal operations
On another test server, I upgraded to the latest 2.2.x httpd I can get
from Amazon, which is 2.2.26. I re-started and still can't seem to use
the ECDHE algorithms.
On that same (second) test server I upgraded to httpd 2.4.9. Here is the
startup log message there:
[Fri Apr 18 15:53:26.330856 2014] [mpm_prefork:notice] [pid 15337]
AH00163: Apache/2.4.9 (Amazon) OpenSSL/1.0.1e-fips PHP/5.5.10
mod_jk/1.2.40 configured -- resuming normal operations
I'm now able to use the ECDHE ciphers.
Everything appears to be dynamically-linked, so I can't understand why
2.2.x reports it's running with OpenSSL 1.0.0 when I clearly have 1.0.1
installed. This is almost certainly an Amazon-Linux-related thing if you
were able to get ECDHE ciphers working on 2.2.x.
I wonder, what does your startup string say about OpenSSL?
The good news is that I really did only have to put it in my ciphers list.
Thanks,
-chris
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Igor Cicimov <ic...@gmail.com>.
On 18/04/2014 2:30 AM, "Hanno Böck" <ha...@hboeck.de> wrote:
>
> On Thu, 17 Apr 2014 12:27:37 -0400
> Christopher Schultz <ch...@christopherschultz.net> wrote:
>
> > I'm trying to enable (and prefer!) ECDHE ciphers for clients that can
> > support them. I've done the obvious:
> [...]
> > I'm running httpd 2.2.23
>
> That's your problem. Get rid of that old cruft. You'll need apache 2.4
> (for that and for many other improvements regarding ssl encryption).
>
No you don't i have 2.2 with latest openssl-1.0.1g on all my servers and
TLSv1.2 and ECDHE ciphers are supported.
> --
> Hanno Böck
> http://hboeck.de/
>
> mail/jabber: hanno@hboeck.de
> GPG: BBB51E42
Re: [users@httpd] Enabling ECDHE ciphers
Posted by Hanno Böck <ha...@hboeck.de>.
On Thu, 17 Apr 2014 12:27:37 -0400
Christopher Schultz <ch...@christopherschultz.net> wrote:
> I'm trying to enable (and prefer!) ECDHE ciphers for clients that can
> support them. I've done the obvious:
[...]
> I'm running httpd 2.2.23
That's your problem. Get rid of that old cruft. You'll need apache 2.4
(for that and for many other improvements regarding ssl encryption).
--
Hanno Böck
http://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: BBB51E42