Hello Stephen,
thanks for your very quick reply.
1) Can it be linked dynamically?
Yes it can.
2) If I would like to link it dynamically when/where do I link the
fipscanister.o?
You build and install fipscanister.o from the FIPS 1.2 test source.
Then obtain the 0.9.8-fips source with shared build options. This will create
libcrypto with fipscanister.o included and linked in the correct manner.
At an application level you just need to link against the OpenSSL shared
libraries.
Let's see if I understood it correctly:
1) If I want to link it dynamically the fipscanister.o is already linked into
the shared object and for static linking the fipscanister.o must be linked
additionally with the fipsld script, because it is not included into the
libcrypto.a.
2) If I would link it static there is no difference between linking to an
application, a *.so or a *.lib.
Are my assumptions correct?
Do you also know about the special handling of the DH-Key-Exchange algorithm?
Bye
Jan
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
