Thanks for the explanation.
> Just link against the library produced by the FIPS capable
> OpenSSL build. If, for some reason, that only produced
> libcrypto.a, then you need to investigate why — perhaps you
> passed “no-shared” when running the config script?
The confusion came from trying to
> On Aug 2, 2016, at 1:59 PM, jonetsu wrote:
>
> The current FIPS User Guide mentions:
>
> "3.3 Creation of Shared Libraries
>
> The FIPS Object Module is not directly usable as a shared
> library, but it can be linked into an application that is a
> shared library.