On 2013-11-01 03:32, Pete Houston wrote:I'm not seeing a lot of options where I could have gone wrong (which maybe means I missed something horrendous). I repeated 'make test' there and saw that it did TLSv1.2 tests. And 'make test' completes okay.
Hello David,
On Fri, Nov 01, 2013 at 03:21:35AM -0700, David Benfell wrote:
I built openssl from source. I'm trying to get TLS 1.2 working,
which the old and crufty openssl on Centos 6.4 doesn't do. Do I need
to do something different to get the development libraries in place?
Since it is the build of ab which fails to link to client methods, did
you correctly build and deploy these with your build of openssl? If so,
you may just need to tell the linker where they are.
Okay, stupid question time: How do I do this? I tried:
Try a standalone test of a TLSv1.2 client method with openssl to see
if you have built these features correctly.
openssl s_client -connect gmail.com:443
This, among other verbiage, seemed to indicate it was using a protocol of TLSv1.2.That would seem to be --with-ssl=/usr/include/openssl , which has lots of fresh .h files. I don't seen anything remotely relevant in /usr/lib .
If it works, just pass
the lib locations on your apache ./configure line (probably using
--with-ssl=DIR).
OTOH, if it fails, you'll probably have to revisit your
build of openssl.
HTH,
Pete
--David Benfell <benfell@xxxxxxxxxxxxxxxxx>
Normally you should expect a GnuPG signature: https://parts-unknown.org/node/2 But this mailer does not support it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|