Skip to content

LibreSSL 3.5.0 has PEM_write_bio_PrivateKey_traditional#499

Closed
vishwin wants to merge 4 commits intoruby:maint-3.0from
vishwin:master
Closed

LibreSSL 3.5.0 has PEM_write_bio_PrivateKey_traditional#499
vishwin wants to merge 4 commits intoruby:maint-3.0from
vishwin:master

Conversation

@vishwin
Copy link

@vishwin vishwin commented Mar 2, 2022

This is the one symbol that currently causes the build to fail when using LibreSSL 3.5.0. They have otherwise added a lot more symbols in this version.

While here, update CI for current LibreSSL versions.

kmdz1 and others added 4 commits February 1, 2022 18:12
…along with some unit tests (ruby#493)

Add OpenSSL::SSL::SSLContext#ciphersuites= method along with unit tests.
I use ruby.git's tool/sync_default_gems.rb and simple git cherry-pick
instead nowadays.

These tasks actually don't correctly work because they use outdated
path references and expect ruby.git to be using git-svn, which is not
the case anymore.

Reported-by: rkoster <hi@rkoster.dev>
Fixes: ruby#495
@rhenium
Copy link
Member

rhenium commented Mar 2, 2022

Thank you for reporting & the patch!

So, the extension currently doesn't compile because EVP_PKEY is an opaque struct in LibreSSL 3.5.0, just like in OpenSSL 1.1.0.

56f0d34 introduced the current code, which was first released as openssl gem version 3.0.0. Could you rebase on top of maint-3.0 branch so I can include it in the next 3.0.x gem release?

(void *)pass)) {
#else
#if OPENSSL_VERSION_NUMBER < 0x10100000 || \
(defined(LIBRESSL_VERSION_NUMBER) && LIBRESSL_VERSION_NUMBER < 0x30500000)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can now use OSSL_OPENSSL_PREREQ() and OSSL_LIBRESSL_PREREQ() macro.

@rhenium rhenium changed the base branch from master to maint-3.0 March 2, 2022 04:49
@rhenium
Copy link
Member

rhenium commented May 27, 2022

The change has been merged by #506.

@rhenium rhenium closed this May 27, 2022
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