[geoff - Fri Jun 4 17:28:58 2004]: > [EMAIL PROTECTED] - Fri Jun 4 11:13:39 2004]: > > I have written new engine module for VIA PadLock ACE. > > > > http://www.logix.cz/michal/devel/padlock/#openssl > > Anyway, please take a look at a recent CVS snapshot from the website and > resubmit your code for that. 0.9.7-stable is maintenance-only unless > under exceptional circumstances, so 0.9.8-dev (HEAD) is where this needs > to go.
OK, attached is a patch against CVS mainline. For me it works in both static and shared versions. > other engines have changed since 0.9.7 for an indication, particularly > with respect to building shared-libs). That said, the OpenBSD-style > cryptodev engine is statically built-in because it only applies for > supported platforms on which it is (presumably) supposed to be the > default. Perhaps the VIA chipset support is a similar thing? (Though > whether openssl's Configure has, or can have, targets that would cover > this remains to be seen.) I didn't get it, sorry. Should I make the Padlock support always static as is the cryptodev? The PadLock is available on new VIA Nehemiah CPUs and if present (and successfully detected by the Padlock engine initialization routine) it should be used, yes. But that's the same situation as with other engines, isn't it? Michal Ludvig ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
