Hi,
The question is related to FIPS compliance.
I need to address public key validation as mentioned in the document -
http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf
(Plausibility test required(section 5.3.3).
It would be very helpful, if i get any suggestion on
Thanks Stephen!
I still have the multiple definitions problem when trying to build on my Mac,
but it works fine when I build in Linux. (Maybe something in my environment).
However, now I run into a problem where my other library expects to link to the
openssl libraries with version number:
In order to track down this error: Is there somebody out there, who has
been able to use a fips-capable openssl with engine_pkcs11 succesfully?
regards
Mathias
On 07/11/2012 12:32 PM, Mathias Tausig wrote:
Hello!
I am trying to sign a certificate with a FIPS enabled build of openssl
An idea:
Would it be possible to create the shared library with the
version number before, not after the extension (.so on unix,
.dll on dos/windows etc.)?
This way Android users could have libssl.1.0.0.so and Windows
users could have ssleay64.1.0.0.DLL.
Linux/Unix users could continue with
