Hi Openssl-Dev Team,
This is Rajesh Kumar from CISCO. We are using the Openssl libraries in our
project in the Win 32 enviroment.
We were using 0.9.8l version of the library earlier. We are now trying to
migrate to 1.0.0a version.
While building the 1.0.0a version we found that few crypto-engines are not
built as part of libeay32.lib. They are built separately as dll's.
In the 0.9.8l version we could see the same getting built as part of the
libeay32.lib.
Below is the difference highlighted,
0.9.8l version export functions from the libeay32.lib:
3218 _ENGINE_load_4758cca
3210 _ENGINE_load_aep
3130 _ENGINE_load_atalla
2708 _ENGINE_load_builtin_engines
3075 _ENGINE_load_chil
2617 _ENGINE_load_cryptodev
3027 _ENGINE_load_cswift
2547 _ENGINE_load_dynamic
3055 _ENGINE_load_nuron
2657 _ENGINE_load_openssl
3532 _ENGINE_load_padlock
2498 _ENGINE_load_private_key
2479 _ENGINE_load_public_key
4046 _ENGINE_load_ssl_client_cert
3211 _ENGINE_load_sureware
2636 _ENGINE_load_ubsec
1.0.0a version:
2475 _ENGINE_init
2708 _ENGINE_load_builtin_engines
2617 _ENGINE_load_cryptodev
2547 _ENGINE_load_dynamic
2657 _ENGINE_load_openssl
2498 _ENGINE_load_private_key
2479 _ENGINE_load_public_key
4046 _ENGINE_load_ssl_client_cert
2515 _ENGINE_new
Now we would like to know if there is any way to get the engines as part of
the library file itself like the 0.9.8l version?
We have our code directly referring to the ENGINE_load_xxxx functions, due
to which the linker errors are seen while using the 1.0.0a version.
I tried to tweak around the no_static_engine variable in the perl file, but
it did not help me much.
Could you please help me out with this as this is very critical for our
product security. Please let me know if you need any further information.
With regards,
Rajesh Kumar R
