On 05/24/2013 06:19 AM, JT Olds wrote:

>> Hello,
>>  It seems that the /dev/crypto device in that system is from an older
>> cryptodev driver. You may want to unload the old module and load the new
>> one.
> This is release 1.6 that I built and deployed. Is there something newer?


No. However your loaded module may differ from the one you built. Are
you sure that the /dev/crypto device corresponds to the one you built?

>>>   DEB_CFLAGS_APPEND='-DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS
>>> -DHASH_MAX_LEN=64' dpkg-buildpackage -us -uc
>>>   cd ..
>>> Notably, the OpenSSL tests pass without /dev/crypto, but when /dev/crypto
>>> exists, the OpenSSL tests fail. Here's the failure:
>> Did you try replacing openssl's eng_cryptodev.c with the included in
>> cryptodev? Does it help with the check and the errors you see?
> No I didn't. I was under the impression from mailing lists and
> otherwise that you hoped to stop maintaining the openssl patch, since
> OpenSSL 1.0.1 and newer had it built in. Should I still be patching
> the latest OpenSSL? I can certainly try that.


I was under the impression the latest openssl included quite a decent
eng_cryptodev.c, but as I understand from your mail it doesn't. My
question is whether the included eng_cryptodev.c fixes the make test
issue? If yes I'd suggest that you report that to the openssl developers.

regards,
Nikos

_______________________________________________
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel

Reply via email to