X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 17 Apr 2012 21:30:00 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: OpenSSL 1.0.1-1 does not seem to support engine aesni Message-ID: <20120417193000.GG22155@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1334688804.85326.YahooMailClassic@web160301.mail.bf1.yahoo.com> <20120417191350.GE22155@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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