Andy Polyakov
Tue, 01 Nov 2005 06:07:26 -0800
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:-)FWIW I'm testing it with OpenVPN having OpenSSL-0.9.8+padlock on one end and OpenSSL-0.9.7 without padlock on the other. And of course I'm regularly running those openssl dgst tests with and without engine on some input files. I don't often send untested patches ;-)
I'm not questioning whether or not the patch is tested! I simply would like to see a record, preferably public one, on *simple* verification procedure, which *anybody* [with appropriate hardware] could execute at any time and in no time, without having to setup VPN or similar. That's all. A.
______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]