Add support for OpenSSL 3

[xfalcox]

This is the same PR sent to the original and adjusted for this fork

See zaru/webpush#106

Co-authored-by: Claire [email protected]

[collimarco]

Thanks for working on this!!

• I have reviewed the code, which seems ok to me, and the tests are passing. My main concern is about set_keys!: I wonder if there is a simpler alternative to create an OpenSSL::PKey::EC from existing base64 keys (also for performance)
• Ruby team is still working on compatibility: Support OpenSSL 3.0 ruby/openssl#369
• The Docker images for Ruby and Debian stable still use OpenSSL v1.1: OpenSSL 3 docker-library/ruby#397

[xfalcox]

The Docker images for Ruby and Debian stable still use OpenSSL v1.1: OpenSSL 3 docker-library/ruby#397

Our image too is based on debian stable, but without this booting the app in development is broken for every dev using Arch, Ubuntu, Fedora, or any up to date distro, which is too much friction for us.

No worries tho, we will fork this and use our fork then.

[collimarco]

Yes, sure, you can use a fork in the meantime.

I will certainly merge this pull request (or equivalent) as soon as Debian stable uses OpenSSL v3 (i.e. when Bookworm becomes stable). Maybe I can merge even before that, but let me think about that.

Please feel free to suggest any other fixes / improvements to this library and I will be happy to merge them.

[collimarco]

Related: ruby/openssl#369 (comment)

Basically the future versions of the openssl gem will provide a method for creating the curve directly from the keys, without ASN1. The new method is in C, so probably performance are better. In any case, at the moment, the correct solution is the one presented in this pull request.

[collimarco]

@xfalcox I am planning to release a v3 of this gem with compatibility with OpenSSL v3.

I would like to merge this pull request, but it should not include the commit for Ruby 2.7, because it is not related to this issue.

• Can you remove that second commit from this pull request so that I can merge? Can you also increase the major VERSION number of this gem to v3.0.0?
• Otherwise, is it ok for you if I just copy your code and create the new release?

[collimarco]

I have released v3 of this gem, which is compatible with both OpenSSL 1.1 and OpenSSL 3 🎉

I have also added @xfalcox and @ClearlyClaire to co-authors of the commit. Thanks for the contributions.

[xfalcox]

Cool, moved back into your fork in discourse/discourse#19849