I just would like to verify this is correct. I've been digging through the
manuals but it would nice to just have a verification.

1) I plan to build a build environment (for Linux and Windows) that matches
what is specified in the 140sp1747.pdf and build the fipscanister

2) Then build openssl-fips with the generated fipscanister in my normal
build environment

3) And use fipsld in my normal build environment to link it into my
application

4) My application will also only use openssl-fips for crypto

5) I plan to document the above process


 Assuming, I transfer the binaries over a 'secure path', I can assert that
my application uses "a validated fips component" ?
Also, if you link openssl-fips into a shared library then link your
application against the shared library, do you have to do the shared link
over fipsld? I'm assuming that you do not.

Reply via email to