On Sat, 17 Mar 2012, Paul Howarth wrote:

I'm able to work around this for now by disabling the AES-CTR detection in configure, by doing:

export ac_cv_func_EVP_aes_128_ctr=no

Thanks for this! How about the attached patch, is that enough to make it build and work without that work-around you found?

--

 / daniel.haxx.se
From f770a3ac1cf778da010b282c94c9e8b45c35fac2 Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <dan...@haxx.se>
Date: Sat, 17 Mar 2012 22:45:56 +0100
Subject: [PATCH] aes: the init function fails when OpenSSL has AES support

The internal init function only worked fine when the configure script
didn't detect the OpenSSL AES_CTR function.

Bug: http://www.libssh2.org/mail/libssh2-devel-archive-2012-03/0111.shtml
Reported by: Paul Howarth
---
 src/openssl.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/openssl.c b/src/openssl.c
index 40818c0..9220868 100644
--- a/src/openssl.c
+++ b/src/openssl.c
@@ -362,6 +362,8 @@ void _libssh2_init_aes_ctr(void)
     _libssh2_EVP_aes_256_ctr();
 }
 
+#else
+void _libssh2_init_aes_ctr(void) {}
 #endif /* LIBSSH2_AES_CTR */
 
 /* TODO: Optionally call a passphrase callback specified by the
-- 
1.7.9.1

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel

Reply via email to