On Tue, Aug 02, 2016, jonetsu wrote:
> FIPS: Need to use FIPS versions of (EVP) methods ?
>
> In FIPS mode, is there a need to use the FIPS_* methods instead of the
> regular ones once FIPS_mode_set(1) was successfully executed ? For
> instance, is there a need to use FIPS_evp_sha1() instead of
FIPS: Need to use FIPS versions of (EVP) methods ?
In FIPS mode, is there a need to use the FIPS_* methods instead of the
regular ones once FIPS_mode_set(1) was successfully executed ? For
instance, is there a need to use FIPS_evp_sha1() instead of EVP_sha1()
? Wouldn't the FIPS version of EVP_s
On 08/02/2016 10:38 AM, jonetsu wrote:
> Hello,
>
> Is it normal to get a 'linker imput file unused because linking
> not done' warning when compiling C code that uses OpenSSL in FIPS
> mode, hence using fipsld ?
>
> The object file is actually generated,a s well as the executable,
> and it does ex
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. A “FIPS compatible” OpenSSL distribution will
automatically incorporate an avai
Hello,
Is it normal to get a 'linker imput file unused because linking
not done' warning when compiling C code that uses OpenSSL in FIPS
mode, hence using fipsld ?
The object file is actually generated,a s well as the executable,
and it does execute in a meaningful manner.
The warning:
[...]