Thanks Murugesh. I just wanted to add that the FOM (OpenSSL FIPS object
module) is built using the instructions provided by the User Guide:
./config
make
make install
The built fipscanister.o is integrated into the OpenSSL distribution via
our own build infrastructure by mimicking the OpenSSL
On Tue, Jul 7, 2020 at 12:48 AM Dr Paul Dale wrote:
> OpenSSL 1.0.2 ceased being supported at the beginning of this year.
>
> If you are deviating in any way from the prescribed build instructions
> (you did read the security policy didn’t you?) you are not FIPS compliant.
>
Can you confirm
Hi,
Yes. You have to use openssl provided build files.
Thanks,
Murugesh P.
On 7/7/20, Shirisha Dasari via openssl-users wrote:
> Hi All,
>
> We have been trying to integrate FOM 2.0.13 with OpenSSL 1.0.2u for FIPS
> compliance. Post integration, we have been able to run in FIPS mode, with
>
OpenSSL 1.0.2 ceased being supported at the beginning of this year.
If you are deviating in any way from the prescribed build instructions (you did
read the security policy didn’t you?) you are not FIPS compliant.
Not using the OpenSSL Makefile is such a deviation. My suspicion is that you
are
Hi All,
We have been trying to integrate FOM 2.0.13 with OpenSSL 1.0.2u for FIPS
compliance. Post integration, we have been able to run in FIPS mode, with
all self-tests passing as well. However, we seem to be encountering issues
in creation and parsing of ECDSA keys.
A little background on how
