You can register both ciphers and digests. For an example,
and easy to read one is the crypto/engine/eng_cryptodev.c
(from the openssl-0.9.8g package), it supports both AES
and 3DES. You shouldn't need to modify OpenSSL's engine
interface at all, just write _your_ engine.

If you're on linux, you might also want to look at ... It provides a Linux cryptodev
interface (ported from the BSDs) and a kernel-level
FreeScale SEC driver. It also provides the necessary
patches for OpenSSL 0.9.8g to support the linux cryptodev.
I don't know how the FreeScale SEC relates to PowerQUICC,
but it might be useful for your efforts.


Mauro Antonelli wrote:
> Hi all,
> I'm going to write an engine to use the Freescale PowerQUICC 2.X
> security engine (this is part of my thesis for the Informatic
> Engineering degree)
> Studying documentation and OpenSSL code I have seen that the engine
> interface do not support neither 3DES nor AES (the only chipers
> supported by the PowerQuicc processor).
> Is reasonably feasible to modify the engine interface? Any suggestions?
> Thanks
> Mauro Antonelli
> __________________________________________________ ____________________
> OpenSSL Project
> Development Mailing List
> Automated List Manager

__________________________________________________ ____________________
OpenSSL Project
Development Mailing List
Automated List Manager