[#81999] [Ruby trunk Bug#13737] "can't modify frozen String" when installing bundled gems — ko1@...
Issue #13737 has been updated by ko1 (Koichi Sasada).
4 messages
2017/07/11
[#82005] [Ruby trunk Bug#13737] "can't modify frozen String" when installing bundled gems — nobu@...
Issue #13737 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2017/07/12
[#82102] Re: register_fstring_tainted:FL_TEST_RAW(str, RSTRING_FSTR) — Eric Wong <normalperson@...>
Koichi Sasada <ko1@atdot.net> wrote:
4 messages
2017/07/18
[#82151] [Ruby trunk Feature#13637] [PATCH] tool/runruby.rb: test with smallest possible machine stack — Rei.Odaira@...
Issue #13637 has been updated by ReiOdaira (Rei Odaira).
3 messages
2017/07/24
[ruby-core:82188] [Ruby trunk Misc#13771] Digest, Ruby OpenSSL, OpenSSL v1.1.0
From:
nobu@...
Date:
2017-07-27 03:45:48 UTC
List:
ruby-core #82188
Issue #13771 has been updated by nobu (Nobuyoshi Nakada). MSP-Greg (Greg L) wrote: > Where I noticed potential issues is that std-lib openssl is a gem, but std-lib digest is not. Hence, thru system updates, the two std-libs could be using different versions of OpenSSL... > > Would 'gemifying' digest help with this? I think that it can happen even if both are installed as gems. ---------------------------------------- Misc #13771: Digest, Ruby OpenSSL, OpenSSL v1.1.0 https://bugs.ruby-lang.org/issues/13771#change-65953 * Author: MSP-Greg (Greg L) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- A thanks to everyone involved in 'gemifying' ruby. As I've mentioned before, I'm a windows user, and not a c type. Where I noticed potential issues is that std-lib openssl is a gem, but std-lib digest is not. Hence, thru system updates, the two std-libs could be using different versions of OpenSSL... Would 'gemifying' digest help with this? Note - in 2.4 stable, both libraries can be built with 1.1.0. 2.3 stable cannot, but will install a current openssl gem, and the system package library (MSYS2/MinGW) could have been updated to 1.1.0. I ask this mostly because 2.3 might have an extended life... -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>