This reverts commit 63f40a5be59ac898e87528630568b7890ffcf5fb.

This reverts commit b6da54c7219197eacdbfdca53739686f0bb2d06a.

LibreSSL 3.6 added support for HKDF in EVP. Enable this in ossl_kdf.c.

https://github.com/ruby/openssl/commit/9bdd39a7e2

LibreSSL 3.4 added EVP_DigestSign() and EVP_DigestVerify(). Use them
when available to prepare for the addition of Ed25519 support in
LibreSSL 3.7.

https://github.com/ruby/openssl/commit/475b2bf766

Co-authored-by: "Jeremy Evans" <code@jeremyevans.net>

	Alias init functions

	The extension library has each initialization function named "Init_" +
	basename. If multiple extensions have the same base name (such as
	cgi/escape and erb/escape), the same function will be registered for
	both names.

	To fix this conflict, rename the initialization functions under sub
	directories using using parent names, when statically linking.
	---
	 ext/extmk.rb            | 16 +++++++++++++++-
	 template/extinit.c.tmpl |  2 +-
	 2 files changed, 16 insertions(+), 2 deletions(-)

	[ruby/fiddle] closure: free resources when an exception is raised in
	 Closure.new

	GitHub: GH-102

	https://github.com/ruby/fiddle/commit/81a8a56239
	---
	 ext/fiddle/closure.c | 56 ++++++++++++++++++++++++++++++++++++++++------------
	 1 file changed, 43 insertions(+), 13 deletions(-)

	[ruby/fiddle] closure: follow variable name change

	GitHub: GH-102

	https://github.com/ruby/fiddle/commit/2530496602
	---
	 ext/fiddle/closure.c | 2 +-
	 1 file changed, 1 insertion(+), 1 deletion(-)

* Copy cvar table on clone

When a class with a class variable is cloned we need to also copy the
cvar cache table from the original table to the clone. I found this bug
while working on fixing [Bug #19379]. While this does not fix that bug
directly it is still a required change to fix another bug revealed by
the fix in https://github.com/ruby/ruby/pull/7265

This needs to be backported to 3.2.x and 3.1.x.

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>

* Fix cvar caching when class is cloned

The class variable cache that was added in
https://github.com/ruby/ruby/pull/4544 changed the behavior of class
variables on cloned classes. As reported when a class is cloned AND a
class variable was set, and the class variable was read from the
original class, reading a class variable from the cloned class would
return the value from the original class.

This was happening because the IC (inline cache) is stored on the ISEQ
which is shared between the original and cloned class, therefore they
share the cache too.

To fix this we are now storing the `cref` in the cache so that we can
check if it's equal to the current `cref`. If it's different we don't
want to read from the cache. If it's the same we do. Cloned classes
don't share the same cref with their original class.

This will need to be backported to 3.1 in addition to 3.2 since the bug
exists in both versions.

We also added a marking function which was missing.

Fixes [Bug #19379]

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>

* Add missing write barrier

We were missing the write barrier for class_value to cref. This should
fix the segv we were seeing in http://ci.rvm.jp/logfiles/brlog.trunk-gc-asserts.20230601-165052

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>

---------

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>