libssh2: [libssh 1.10.1_dev] Error "Invalid MAC received" when building without HAVE_EVP_AES_128_CTR

Using libgit2 + libssh2 + openssl 1.1.1 compiled with mingw-w64. After upgrading from 1.10.0 to 1.10.1_dev (master branch) cloning git+ssh repos from GitHub fails with:

Error in libgit2::git_clone : failed to start SSH session: Invalid MAC received

Reverting to libssh2 1.10.1 fixes the problem, so there seems to be a regression. Afaict, the issue only appears on Windows. What recent changes could be causing this?

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (19 by maintainers)

Commits related to this issue

Revert usage of EVP_CipherUpdate #764 #739 The behavior is different which is causing it to not work as expected. — committed to libssh2/libssh2 by willco007 2 years ago
Revert usage of EVP_CipherUpdate #764 #739 (#765) Revert usage of EVP_CipherUpdate from wolfSSL PR to fix #764 #739. — committed to libssh2/libssh2 by willco007 2 years ago
openssl: require v1.0.2, make HAVE_EVP_AES_128_CTR always on Fixes #739 — committed to vszakats/libssh2 by vszakats a year ago
openssl: require v1.0.2, make HAVE_EVP_AES_128_CTR always enabled libssh2 built with OpenSSL and without its HAVE_EVP_AES_128_CTR option are working incorrectly. This option wasn't always auto-detect... — committed to vszakats/libssh2 by vszakats a year ago
openssl: require v1.0.2, make HAVE_EVP_AES_128_CTR always enabled libssh2 built with OpenSSL and without its `HAVE_EVP_AES_128_CTR` option are working incorrectly. This option wasn't always auto-dete... — committed to vszakats/libssh2 by vszakats a year ago
openssl: require v1.0.2, make HAVE_EVP_AES_128_CTR always enabled libssh2 built with OpenSSL and without its `HAVE_EVP_AES_128_CTR` option are working incorrectly. This option wasn't always auto-dete... — committed to vszakats/libssh2 by vszakats a year ago
openssl: require `EVP_aes_128_ctr()` support libssh2 built with OpenSSL and without its `EVP_aes_128_ctr()`, aka `HAVE_EVP_AES_128_CTR` option are working incorrectly. This option wasn't always auto-... — committed to vszakats/libssh2 by vszakats a year ago
openssl: require `EVP_aes_128_ctr()` support libssh2 built with OpenSSL and without its `EVP_aes_128_ctr()`, aka `HAVE_EVP_AES_128_CTR`, option are working incorrectly. This option wasn't always auto... — committed to vszakats/libssh2 by vszakats a year ago
openssl: require `EVP_aes_128_ctr()` support libssh2 built with OpenSSL and without its `EVP_aes_128_ctr()`, aka `HAVE_EVP_AES_128_CTR`, option are working incorrectly. This option wasn't always auto... — committed to vszakats/libssh2 by vszakats a year ago
libssh2: prepare for always-on openssl EVP_aes_128_ctr [ci skip] Ref: https://github.com/libssh2/libssh2/commit/ec0a51db1f69eafa14ead6d17e6aca13075c034b Ref: https://github.com/libssh2/libssh2/issues... — committed to curl/curl-for-win by vszakats a year ago
openssl: require `EVP_aes_128_ctr()` support libssh2 built with OpenSSL and without its `EVP_aes_128_ctr()`, aka `HAVE_EVP_AES_128_CTR`, option are working incorrectly. This option wasn't always auto... — committed to Bob2019-li/libssh2 by vszakats a year ago

Most upvoted comments

I think the best solution here is to remove the option to build without HAVE_EVP_AES_128_CTR. I think all openssl versions have this function, the only reason why it is not set is that autoconf fails to detect it.

jeroen on Sep 9, 2022