My issue was that my server certificate was not SHA-256 capable. As soon
as I put a new server certificate out there it started working.
From: Jerry Blasdel/USA/CSC@CSC
To: users@httpd.apache.org
Date: 04/03/2014 11:53 AM
Subject:[users@httpd] Apache HTTPD SHA256
We have
We have built the following:
httpd-2.4.6
openssl-1.0.1.e
openssl-fips-2.05
for both Windows and Solaris so we can leverage SHA256.
For both environments I have Apache configured with the following:
SSLProtocol +TLSv1 +TLSv1.1 +TLSv1.2
On Windows, this works. I can use a Browser to hit the ser
us by e-mail of the mistake in
delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.
From: Jerry
We are trying to get an Apache 2,4 HTTPD executable created from a
Fips-capable OpenSSL on Solaris.
After building and running the tests on fips-2 and OpenSSL 1.0.1c we
build Apache and when we try to start it up we get the following in the
error_log:
[Wed Jan 09 16:21:30.066478 2013] [ssl:e
