ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "rhenium (Kazuki Yamaguchi)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:109849] [Ruby master Bug#18999] Backport openssl 2.1.4/2.2.2/3.0.1
Date: Thu, 08 Sep 2022 14:58:00 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-18999.20220908145759.9231@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-18999.20220908145759.9231@ruby-lang.org

Issue #18999 has been reported by rhenium (Kazuki Yamaguchi).

----------------------------------------
Bug #18999: Backport openssl 2.1.4/2.2.2/3.0.1
https://bugs.ruby-lang.org/issues/18999

* Author: rhenium (Kazuki Yamaguchi)
* Status: Closed
* Priority: Normal
* Backport: 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED
----------------------------------------
Please backport the latest openssl to stable branches.

I created GitHub PRs for each branch:

 - Ruby 2.7 (v2.1.4) https://github.com/ruby/ruby/pull/6339
 - Ruby 3.0 (v2.2.2) https://github.com/ruby/ruby/pull/6338
 - Ruby 3.1 (v3.0.1) https://github.com/ruby/ruby/pull/6337

Patches for Ruby 2.7 and 3.0 just contain a bugfix for the handling of pkg-config/--with-openssl-dir option (https://github.com/ruby/openssl/pull/486, also [Bug #18763]). This would be useful for systems that have multiple versions of OpenSSL installed.

Patch for Ruby 3.1 contains several regression fixes in addition.



-- 
https://bugs.ruby-lang.org/

           reply	other threads:[~2022-09-08 14:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <redmine.issue-18999.20220908145759.9231@ruby-lang.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-18999.20220908145759.9231@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).