[openssl-dev] [crypto engine]: API users try to find separate external library for new engine

[Alexander Gostrer]

Hi Cata,

We solved this problem in our project:
https://github.com/AtmelCSO/cryptoauth-openssl-engine
I may be wrong but I think it was done using "export LD_LIBRARY_PATH=<your
lib path>". Try it. If it will not work then you dig into our engine.

Regards,
Alex Gostrer

On Wed, Feb 3, 2016 at 9:00 AM, Catalin Vasile <cata.vasile at nxp.com> wrote:

>
>
> I'm trying to make a new crypto engine.
>
> Any application that tries to use my custom OpenSSL library that includes
> my engine gives me an error trying to find an external library for my new
> engine (it tries to locate /usr/lib/libhwrng.so,  where hwrng is my
> engine), although if I run a "grep -R 'hwrng' . " in the install folder it
> finds references in the libcrypto.so .
>
> I have done a "grep -R 'cryptodev' ." and it is referenced the same amount
> of times and in the same files.
> What could I be missing that cryptodev is loaded "naturally" (it knows
> it's inside libcrypto.so), but engine hwrng is seen as being something
> totally external?
>
>
> Cata
>
>
>
> _______________________________________________
> openssl-dev mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20160203/a6d8df34/attachment.html>