-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EVP_DigestSignInit: unsupported (OpenSSL::HMACError)
and Digest initialization failed: initialization error (OpenSSL::Digest::DigestError)
#642
Comments
These errors looks started since Ruby 3.1 and 3.2 base image changed from "bullseye" to "bookworm" and these errors have been workarounds by using Debian "bullseye" based Docker image at Rails CI. rails/buildkite-config#47 |
Looks like https://wiki.openssl.org/index.php/OpenSSL_3.0
|
Duplicate of #500. Yes - the implementation of MD4 belongs to the Since MD4 is obsolete in every sense and is apparently only used in the test suite (https://github.com/rails/rails/blob/87ab32f72a494ea18a4e2335becaebb66f5ce673/activesupport/test/rotation_coordinator_tests.rb#L100), I'd suggest simply replacing it with a modern digest algorithm. |
Thanks for the update. rails/rails#48493 will replace |
This issue is reported initially at rails/rails#48483 and here is Ruby script to reproduce this error.
The original issue has two exceptions.
EVP_DigestSignInit: unsupported (OpenSSL::HMACError)
andDigest initialization failed: initialization error (OpenSSL::Digest::DigestError)
EVP_DigestSignInit: unsupported (OpenSSL::HMACError)
Steps to reproduce
Expected behavior
It should run as Ruby 3.0.5 does.
Actual behavior
It gets "EVP_DigestSignInit: unsupported (OpenSSL::HMACError)" with Ruby 3.2.2.
Digest initialization failed: initialization error (OpenSSL::Digest::DigestError)
Steps to reproduce
Expected behavior
It should run as Ruby 3.0.5 does.
Actual behavior
The text was updated successfully, but these errors were encountered: