Subject: Re: AES-CTR not available upon configure ibssh2 1.2.6

Re: AES-CTR not available upon configure ibssh2 1.2.6

From: Simon Josefsson <simon_at_josefsson.org>
Date: Thu, 05 Aug 2010 23:14:34 +0200

"A. Mark" <gougolith_at_gmail.com> writes:

> Hello!
>
> I noticed this upon ./configure...
>
> Crypto library: openssl: no (AES-CTR: N/A) libgcrypt: yes
>
> ...the same if forcing openssl, it's on a linux box, but I'm just
> wondering if the aes 256 cipher would stil be working regardless of
> this aes function not being detected?

AES-CTR is always supported by libssh2. The AES-CTR print above tells
you whether your OpenSSL has AES-CTR or not. If you built OpenSSL
yourself, chances are that it does, but most distributions appears to
built OpenSSL without AES-CTR. If your OpenSSL doesn't have AES-CTR,
libssh2 implements it internally instead.

/Simon
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2010-08-05