Hi all, I'm looking for anyone who's using openssl on 386 (and perhaps 486) chip models that might be able to verify a patch before it gets applied? The RT ticket about this is at; http://www.aet.tu-cottbus.de/rt2/Ticket/Display.html?id=889 and the code it refers to is at; http://www.logix.cz/michal/devel/padlock/
To verify this adequately, please take a recent CVS snapshot (or checkout) of openssl (it. not any 0.9.* stable branches) and compile and run something first (eg. "openssl speed"). Then after applying the "openssl-0.9.8cvs-padlock.diff" patch from Michal's site, please compile and run again. It would also be useful to verify that the hook into Michal's detection code is being run, so please insert a printf into the padlock_insn_cpuid_available() function in crypto/engine/eng_padlock.c so you can see if it's being called when running programs. Note, this could should be bypassed except when gcc is being used, so VC++ is unlikely to be informative (though using cygwin tools might be interesting). Any feedback on this would be most useful, as this feature is only supported on certain x86 chips and so we can't commit unless the detection code is seen to be safe on the remaining x86 chips, particularly older ones without cpuid. Regards, Geoff -- Geoff Thorpe [EMAIL PROTECTED] http://www.geoffthorpe.net/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
