On Apr 17 20:19, Nick Lowe wrote: > In 1.0.1: > > http://www.openssl.org/news/changelog.html > > "Add RC4-MD5 and AESNI-SHA1 "stitched" implementations. > > This work was sponsored by Intel. > [Andy Polyakov]"
I didn't mean to imply that there's no new aesni mode, but if you take a look into the sources you will see no *engine* for aesni. An engine is an external shared object which is implemented in the engines subdir in the source tree. There is no such code nor anything in the engines/Makefile pointing to a new aesni engine. Aesni-related code is only in the crypto/evp subdir, so I assume it's implemented as part of the base libs. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
