Christopher Marshall wrote:
I have a question about the FIPS 140-2 status of the openssl command line tool.
If I successfully compile openssl-fips-1.1.1 to obtain an openssl command line
tool linked against
it (fipscanister.o), and I use that openssl commandline tool to encrypt a file
with a FIPS
approved cipher (for example, AES), would that use be considered FIPS 140-2
compliant?
Short answer; no. There's more to running an application in FIPS
approved mode than just linking against a properly generated
fipscanister.o. Please refer to the definitive reference, the Security
Policy (http://csrc.nist.gov/cryptval/140-1/140sp/140sp733.pdf),
especially sections 4 and 5. The User Guide at
http://www.openssl.org/docs/fips/UserGuide-1.1.1.pdf may also be of value.
In particular your application *must* actively enable FIPS mode, which
is done via a call to FIPS_mode_set(). If the OPENSSL_FIPS environment
variable is set the openssl command does so, but this feature is really
only intended for testing purposes.
-Steve M.
--
Steve Marquess
[EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]