Thanks Steve. So basically the idea is to allow companies build the OpenSSL with FIPS modules in their product and ship only this version of OpenSSL to all their customers. For the customers who don't need FIPS, then just simply keep the FIPS mode disabled and then the OpenSSL will behave just like there's no FIPS module exist. Is that correct? One question I have is, in the above case should the openssl commands also remain FIPS disabled unless we explicitly enable FIPS mode? I built a OpenSSL lib with FIPS modules, and what I found was, when I run the following command to create non-FIPS compliant checksum (i.e. MD5 in this case), it failed with some MD5 algorithm not permitted errors. openssl dgst -md5 FILE_NAME To me it looks like the openssl commands are always run with FIPS enabled in this case. Is that the expected behavior? Thanks. On Tue, Jan 19, 2016 at 6:44 AM, Steve Marquess <marquess at openssl.com> wrote: > On 01/19/2016 04:33 AM, security veteran wrote: > > Hi, > > > > I am trying to build a system with both the non-FIPS OpenSSL and the > > OpenSSL with FIPS modules, and was wondering does OpenSSL FIPS modules > > actually only affect libcrypto.so? > > Yes and no. > > The "FIPS enabled" OpenSSL consists of OpenSSL 1.0.N built with the > "fips" option, in the presence of an OpenSSL FIPS module. That module > (which is basically the fipscanister.o file) is embedded within the > libcrypto shared library. > > If you don't enable FIPS mode (no FIPS_mode_set() call) then that > libcrypto behaves just like the usual libcrypto from a non-FIPS enabled > OpenSSL build; the FIPS module is just dead weight. > > But once you enable FIPS mode then the cryptographic operations that are > not allowed by FIPS 140-2 (which is many of the algorithms supported by > OpenSSL) are automagically disabled. Those cryptographic operations > which are allowed are routed to the FIPS module. Note that those > separate crypto implementations in the FIPS module will always > necessarily be "behind" the ones on OpenSSL proper (in terms of > performance, security, general robustness). > > Note we designed the "FIPS enabled" mechanism just so that vendors would > not need to ship two different sets of binaries to their customers who > do and don't care about FIPS 140-2. Ship the "FIPS enabled" OpenSSL > libraries to all your customers, and those who don't explicitly enable > FIPS mode won't see the FIPS part. > > -Steve M. > > -- > Steve Marquess > OpenSSL Software Foundation > 1829 Mount Ephraim Road > Adamstown, MD 21710 > USA > +1 877 673 6775 s/b > +1 301 874 2571 direct > marquess at openssl.com > gpg/pgp key: http://openssl.com/docs/0x6D1892F5.asc > _______________________________________________ > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160119/c9aee353/attachment-0001.html>
