Skip to content

Suppress OpenSSL-3 warnings #576

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

Merged
merged 2 commits into from
Dec 22, 2022
Merged

Suppress OpenSSL-3 warnings #576

merged 2 commits into from
Dec 22, 2022

Conversation

nobu
Copy link
Member

@nobu nobu commented Nov 29, 2022

No description provided.

@hsbt
Copy link
Member

hsbt commented Nov 30, 2022

@rhenium We hope to merge this before Ruby 3.2.0-preview4 or final release. Can you look this?

matzbot pushed a commit to ruby/ruby that referenced this pull request Dec 13, 2022
@rhenium rhenium merged commit 1b60365 into ruby:master Dec 22, 2022
@rhenium
Copy link
Member

rhenium commented Dec 22, 2022

Merged, thank you. I agree suppressing the warnings is the best way forward for now.

Those warnings (both casting const pointers and deprecation) are due to the use of the legacy low-level structs.

This is a problem for us not only because of the warnings, but because using a legacy function requires EVP_PKEY to convert itself to a "legacy PKEY" (as opposed to "provided PKEY"), which means we can't use other EVP_PKEY functions that are based on OpenSSL providers, such as EVP_PKEY_todata().

I was hoping we could gradually fix them by replacing them with the appropriate EVP_PKEY API, but this doesn't seem to be possible in the short term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants