From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS24940 94.130.0.0/16 X-Spam-Status: No, score=-2.9 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS, SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [94.130.110.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 85F4F1F61A for ; Tue, 13 Dec 2022 04:35:44 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.b="VJ/e8g85"; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id EBC447E643; Tue, 13 Dec 2022 04:35:37 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=VJ/e8g85; dkim-atps=neutral Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by nue.mailmanlists.eu (Postfix) with ESMTPS id DA0857E630 for ; Tue, 13 Dec 2022 04:35:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=jdYR0WbDv9z2yrnfflXpb+wBhUOoRCn9WbID2BOf2/s=; b=VJ/e8g85jJQrBRSWZxlCIzcR8mod7ZXPT2mXiGHSTqTe/3tN1etnBCX3Q9hLKEs9KyhB snASDv+Fl/Zt0P/+QQPbwSJsl3Ad/iecd95zVdYO39JL7A2InmZqJwEvJmlD0pY9n3DejE dgLMFhAkjqRa1XOmCA/TlAtzlCFCyJbzABTaa7Og1g47XVwg4YgowuAvdxH9wadz/4EOuf dbkfab4lO1NxVeQtBYwe0W176eJQDZGI8S5VyA4n7TNqUfLpguOLnUE4DtMT5BSC/aEZIY ElKXtGCDCy0WyQSp3c5bwdpjm72FFfasueU1PldLBAKpOfRlbMtu1gbYpeDexVBQ== Received: by filterdrecv-6c4ccfbdd8-pvv59 with SMTP id filterdrecv-6c4ccfbdd8-pvv59-1-63980114-11 2022-12-13 04:35:32.323494845 +0000 UTC m=+2179798.582575757 Received: from herokuapp.com (unknown) by geopod-ismtpd-1-1 (SG) with ESMTP id BCf8ianBQxexSX7QIgoqFQ for ; Tue, 13 Dec 2022 04:35:32.195 +0000 (UTC) Date: Tue, 13 Dec 2022 04:35:32 +0000 (UTC) From: "hsbt (Hiroshi SHIBATA)" Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Misc X-Redmine-Issue-Id: 19178 X-Redmine-Issue-Author: Segaja X-Redmine-Issue-Assignee: hsbt X-Redmine-Sender: hsbt X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 87663 X-SG-EID: =?us-ascii?Q?BAqCsB0mvMCnHXWkBD9MTHUyV8AfYOY3mM6FlznSxbO5US8=2FSBDCMBBYmmIAuU?= =?us-ascii?Q?TeaKG5YiQzAGgZc0jHcwXZVFMafO4FzN+zEifU7?= =?us-ascii?Q?=2FXM1+fanuZDnAKbO2EWEkBO=2FkBuUawKrcaOjp3w?= =?us-ascii?Q?CnitRgnLIguBWwQkpx7xaM0JbPIhJz+Bav=2FX23D?= =?us-ascii?Q?lWgFxJ3pDHAqeTSaDKGHBSWPXmwoA4r2aHWE0ak?= =?us-ascii?Q?ZV9L7c5WIhjrYt4aa8LqEmS7HRnZ040qSMbOOkX?= =?us-ascii?Q?wYohIveDUZl4H1YJi5+5A=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: FPMBPOIABFYJBX7YAIPEZV5EIZCQS76V X-Message-ID-Hash: FPMBPOIABFYJBX7YAIPEZV5EIZCQS76V X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:111267] [Ruby master Misc#19178] How does CRuby handle CVE issues in stdlib gems which get patched? List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #19178 has been updated by hsbt (Hiroshi SHIBATA). Assignee set to hsbt (Hiroshi SHIBATA) ---------------------------------------- Misc #19178: How does CRuby handle CVE issues in stdlib gems which get patched? https://bugs.ruby-lang.org/issues/19178#change-100615 * Author: Segaja (Andreas Schleifer) * Status: Closed * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- If there is a CVE issue in one of the stdlibs ( https://stdgems.org/ ) which gets patched, what is CRubys approach on how to push this critical fix to the users? As far as I know stdlibs get only updated for the users if CRuby releases a new version. So will CRuby always release a new version if there is a critical fix an stdlib "needs" to be updated? -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/