Hi Stephen,
I have downloaded ftp://ftp.openssl.org/snapshot/openssl-fips-test-1.2.0.tar.gz,
extracted it and:
./config fipscanisterbuild
make
make install
and then
make clean
./config fips shared no-idea no-mdc2
--with-fipslibdir=/usr/local/ssl/fips-1.0/lib
make depend
make
The libraries have been build and it was possible to load the libcrypto.so
dynamically, to load the FIPS_mode_set function and to call it successfully
(return code 1). But there are many warnings that sound dangerous. I have pasted
some below. Any idea what causes this and how I can avoid it?
Thanks
Jan
evp_pkey.c: In function ‘EVP_PKEY2PKCS8_broken’:
evp_pkey.c:382: warning: function called through a non-compatible type
evp_pkey.c:382: note: if this code is reached, the program will abort
evp_pkey.c: In function ‘dsa_pkey2pkcs8’:
evp_pkey.c:478: warning: function called through a non-compatible type
evp_pkey.c:478: note: if this code is reached, the program will abort
pem_all.c: In function ‘PEM_write_RSAPublicKey’:
pem_all.c:240: warning: function called through a non-compatible type
pem_all.c:240: note: if this code is reached, the program will abort
p5_pbev2.c: In function ‘PKCS5_pbe2_set’:
p5_pbev2.c:167: warning: function called through a non-compatible type
p5_pbev2.c:167: note: if this code is reached, the program will abort
ocsp.c:761: warning: function called through a non-compatible type
ocsp.c:761: note: if this code is reached, the program will abort
rmdtest.c: In function ‘main’:
rmdtest.c:110: warning: dereferencing type-punned pointer will break
strict-aliasing rules
Dr. Stephen Henson wrote:
In the case of a shared library the "application" is the shared library itself
and the fipsld linking has been performed by the build process.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
