Is it possible to build a shared library that incorporates fipscanister.o, where fipscanister.o is already built as per rules specified in users guide and security policy. Is that shared library will be a validated one to be used by an independent application. I have my own shared library which is statically linked with libcrypto.a but now i want to make it fips capable. User guide mostly talks about static linking of object module directly with the application using fipsld. For shared library do i still need to use fipsld and if yes how to use it to correctly create a shared library.
On Mon, Apr 11, 2011 at 5:57 PM, raghib nasri <raghibna...@gmail.com> wrote: > Hi, > I want to create shared library by statically linking my object file > with libcrypto.a. I am using the following command > FIPSLD_CC=g++ /usr/local/ssl/fips/bin/fipsld -shared -fPIC -o > libshared.so libfips.o -L/usr/local/ssl/fips/lib/libcrypto.a > > it gives the following error: > > /usr/local/ssl/fips/bin/fipsld: line 94: > /usr/local/ssl/fips/bin/../fips/fips_standalone_sha1: No such file or > directory > 1d0 > < HMAC-SHA1(fips_premain.c)= 9e5ddba185ac446e0cf36fcf8e1b3acffe5d0b2c > /usr/local/ssl/fips/bin/../lib/fips_premain.c fingerprint mismatch > > Can anyone help me for the error and suggest correct way for building > shared library for fips object module. > >
