X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20120417193000.GG22155@calimero.vinschen.de> References: <1334688804 DOT 85326 DOT YahooMailClassic AT web160301 DOT mail DOT bf1 DOT yahoo DOT com> <20120417191350 DOT GE22155 AT calimero DOT vinschen DOT de> <20120417193000 DOT GG22155 AT calimero DOT vinschen DOT de> Date: Tue, 17 Apr 2012 20:35:44 +0100 Message-ID: Subject: Re: OpenSSL 1.0.1-1 does not seem to support engine aesni From: Nick Lowe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Oh, sorry, yes. I suspect that the AES-NI instructions are used 'silently' where supported by the processor. -- 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