-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dr. Stephen Henson wrote on 04/08/2010 08:16 PM:
On Thu, Apr 08, 2010, Gatewood (Woody) Green wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Setup:
Built openssl-fips-1.2 per the Security Policy.
Built openssl-0.9.8n
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Setup:
Built openssl-fips-1.2 per the Security Policy.
Built openssl-0.9.8n with the fips option
Notes:
Successfully built FIPS-ified version of wget, curl/libcurl, libssh2
and mod_ssl. Successfully means the work as advertised within the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
William A. Rowe Jr. wrote on 03/31/2010 01:20 AM:
On 3/30/2010 10:58 AM, Gatewood (Woody) Green wrote:
I assume the 2010 limit on new validations is the impending finalization
of 140-3.
What you are thinking of won't be designated 140-3
on new validations is the impending finalization
of 140-3.
As a foot note, having obtained certification previously on a subset of
our products, I understand and well appreciate the cost and headache
factors involved.
Thanks,
Woody
Steve Marquess wrote on 03/29/2010 06:47 PM:
Gatewood (Woody
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I noticed in trying to build OpenSSL 1.0.0 that Configure no longer
accepts the fips and --with-fipslibdir= arguments (as does all 0.9.8
version since j for building in conjunction and with inclusion of
openssl-fips-1.2).
Are we awaiting
