Issue with 2.3.5 and "cipher none"
Posted: Fri Nov 07, 2014 7:20 pm
Hi All,
I have compiled and installed the new version 2.3.5 on linux.
I have "cipher none" in my configuration. It doesn't work anymore. It gives this error:
Fri Nov 7 19:47:46 2014 OpenVPN 2.3.5 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Nov 7 2014
Fri Nov 7 19:47:46 2014 library versions: OpenSSL 1.0.1e-fips 11 Feb 2013, LZO 2.03
Fri Nov 7 19:47:46 2014 ******* WARNING *******: null cipher specified, no encryption will be used
Fri Nov 7 19:47:46 2014 ******* WARNING *******: null MAC specified, no authentication will be used
Fri Nov 7 19:47:46 2014 Assertion failed at crypto_openssl.c:523
Fri Nov 7 19:47:46 2014 Exiting due to fatal error
I have copied the file crypto_openssl.c from version 2.3.2 and done a few changes to make it compile on version 2.3.5. And now it works and accepts "cipher none" configuration. My patch is not very clean as it basically removes most of the added changes to this file.
If it can be helpful, I have noticed the same error in the Windows client version 2.3.5.
Thanks,
Vincenzo
I have compiled and installed the new version 2.3.5 on linux.
I have "cipher none" in my configuration. It doesn't work anymore. It gives this error:
Fri Nov 7 19:47:46 2014 OpenVPN 2.3.5 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Nov 7 2014
Fri Nov 7 19:47:46 2014 library versions: OpenSSL 1.0.1e-fips 11 Feb 2013, LZO 2.03
Fri Nov 7 19:47:46 2014 ******* WARNING *******: null cipher specified, no encryption will be used
Fri Nov 7 19:47:46 2014 ******* WARNING *******: null MAC specified, no authentication will be used
Fri Nov 7 19:47:46 2014 Assertion failed at crypto_openssl.c:523
Fri Nov 7 19:47:46 2014 Exiting due to fatal error
I have copied the file crypto_openssl.c from version 2.3.2 and done a few changes to make it compile on version 2.3.5. And now it works and accepts "cipher none" configuration. My patch is not very clean as it basically removes most of the added changes to this file.
If it can be helpful, I have noticed the same error in the Windows client version 2.3.5.
Thanks,
Vincenzo