Test programs [extra -e argument perhaps].
... to enable engines?
Yes. On the other hand I suppose one can write a script, which would
simply call 'openssl dgst -sha[1|256] -engine padlock' with a set of
known input vectors...
Could be. But should it be run automatically
during make? I guess no...
No, but I'd like to *see* some test program and I'd like to hear
explicit statement that the implementation passes this test. As you
might recall we have tested AES by encypting with software and
decrypting with engine and then other way around. We need something even
this time:-) A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
