From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95223] [Ruby master Bug#16238] Publish new WEBrick version to rubygems.org
Date: Fri, 04 Oct 2019 13:41:32 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-81896.20191004134131.c28e3cb9800153aa@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16238.20191004132159@ruby-lang.org
Issue #16238 has been updated by hsbt (Hiroshi SHIBATA).
Assignee set to hsbt (Hiroshi SHIBATA)
Status changed from Open to Assigned
I'm working on it now. I need to triage the changeset from ruby/ruby master.
Please wait a few days.
----------------------------------------
Bug #16238: Publish new WEBrick version to rubygems.org
https://bugs.ruby-lang.org/issues/16238#change-81896
* Author: rbjl (Jan Lelis)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version:
* ruby -v:
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The latest security releases of Ruby include some fixes in the webrick default gem:
- https://www.ruby-lang.org/en/news/2019/10/01/webrick-regexp-digestauth-dos-cve-2019-16201/
- https://www.ruby-lang.org/en/news/2019/10/01/http-response-splitting-in-webrick-cve-2019-16254/
However, as of now, the changes have not been published to rubygems:
- https://rubygems.org/gems/webrick
More confusingly, the version number of webrick has not be changed yet: https://github.com/ruby/ruby/blob/v2_6_5/lib/webrick/version.rb (still 1.4.2 as before the security patches). This is problematic, because now multiple versions of version 1.4.2 of webrick exist... It also prevents people from quickly resolving the webrick-related security issue by just installing the new version of webrick.
In the past, security patches often led to a fourth-place-version-number (see for example, rubygems itself, or [rdoc](https://github.com/ruby/ruby/commit/8c57255f87e2a70a033d9b1e2bdd474bc1ba6cc5))
I suggest that a new version of webrick should be released to rubygems. I am also curious about how the process of dealing with similar issues in the future can be optimized
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-10-04 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16238.20191004132159@ruby-lang.org>
2019-10-04 13:22 ` [ruby-core:95222] [Ruby master Bug#16238] Publish new WEBrick version to rubygems.org mail
2019-10-04 13:41 ` hsbt [this message]
2019-10-04 13:53 ` [ruby-core:95224] " hsbt
2019-10-04 13:58 ` [ruby-core:95225] " mail
2019-10-04 15:34 ` [ruby-core:95227] " mail
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.journal-81896.20191004134131.c28e3cb9800153aa@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).