-
Notifications
You must be signed in to change notification settings - Fork 254
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
Compability issue with OpenSSL 3.0 #381
Comments
Ubuntu 22.04 LTS was released in April, which ships only with OpenSSL 3 and not OpenSSL 1.1. As such, could this be prioritised? Many thanks :-) |
Yup, just hit this on upgrading my heroku buildpack to 22. |
Ok, so the script seems all good. The idea is to notify me to check to see if any new updates support the heroku 22 stack, as per issue here: googleapis/google-auth-library-ruby#381 It's an OpenSSL issue. I'm not in a big hurry - this stack will be supported until April 2025 - but it would be nice to keep up.
hey, would love to get an update for this issue. any timeline or fixes we can implement? |
I would love to get an update on this too 🙂 |
Yes, I can't even dev on macOS like this! Thankfully I'm mostly a windows guy. |
...does anybody have a workaround for local dev? How do I force the use of 1.1 on a new install of macOS? |
I wonder if I can patch this? Here's other places where they've solved the problem: https://bugs.launchpad.net/ubuntu/+source/ruby-net-ssh/+bug/1964025/comments/9 Don't know if I have the time right now to dive into it, but lemme see. |
Oh, also, left a comment on the most relevant OpenSSL issue to link these together and to request docs/suggestions on patching this. See: ruby/openssl#369 (comment) |
Ok, sorry to triple post, but this does seem fixable with @nov's patch in nov/json-jwt#102. I'm too out of my depth to make the changes... I'm not a cryptographer, so I strongly hesitate to change anything that handles cryptography. That's the origin of many a bug and a timing attack :) |
hi we also want to know when this will be fixed. |
draft solution is available in the branch here https://github.com/googleapis/google-auth-library-ruby/tree/fix_openssl3_compatibility Please let us know of any issues @dataf3l |
Trying patch for issue googleapis/google-auth-library-ruby#381, seems to work! googleapis/google-auth-library-ruby#397
Seems to work! Lets get some eyes on this PR! |
Looks like the patch is still waiting on the review! Glad to see that Google cares about code quality. It would be better if they assigned enough engineers to the job so that they wouldn't be so overworked 🤣😭 Is a shame they're talking about cutbacks and layoffs. Such a typical American corporation... From two cow economics:
(To be clear, I'm saying that the engineers are doing a good job, definitely not that it's their fault) |
We've completed additional testing on the patch and merged it. There's currently a release freeze in place due to Next which takes place next week. We'll release after the conference ends, around Oct 14. |
Yay! I wish there was an alpha release I could use for now, but totally am glad as is. Thanks for fixing. |
The current version of the gem does not seem to be compatible with OpenSSL 3.0. The problem seems to be that pkeys are immutable in OpenSSL 3.
Environment details
Steps to reproduce
ruby -e 'require "openssl"; p OpenSSL::::OPENSSL_VERSION'
report version 3.0.0toys do test
OpenSSL::PKey::PKeyError: rsa#set_key= is incompatible with OpenSSL 3.0
OpenSSL::PKey::PKeyError: pkeys are immutable on OpenSSL 3.0
The text was updated successfully, but these errors were encountered: