You just need to add the required libraries and the openSSL include path in
your .pro file (Like you do with any third party tools).
Then you need to put the openssl .dll or .so files near your executable or
in a standard path. It should do.
On Mon, Mar 18, 2013 at 1:53 AM, Jevin Sonut wrote:
>
Hello!
I'm currently using the cryptodev framework-engine with openssl-1.0.1e.
By run the command
# openssl engine -t
(cryptodev) cryptodev engine
[ available ]
(dynamic) Dynamic engine loading support
[ unavailable ]
we can see that the cryptodev is the active-chosen engine.
So it s
To whom it may concern,
I try to generate the FIPS Object module for Linux 2.6.32 on a ARMv7
architecture to be included into open-ssl 1.0.1e. It is a validated
configuration based on the my understanding from the 'User Guide - OpenSSL FIPS
Object Module v2.0'.
Can you confirm that the environme
