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)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 42B6B1F601 for ; Sat, 3 Dec 2022 21:20:06 +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="BzYeMlk7"; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 5A8E37E91D; Sat, 3 Dec 2022 21:19:59 +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=BzYeMlk7; 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 E9BCB7E91B for ; Sat, 3 Dec 2022 21:19:54 +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=IQfZ/nDu3LvCs0CcuPYd7Y2iAwz+ii1xsLcvkWnWQCo=; b=BzYeMlk707fF7Kj5wmHceps8PZTQalzrajnSEjWXSjSjs+Btv4NblCwoG65jISKiHjUh R6Q+UxHiT+Akd884uZJih0Rfml3YkPdssEM+rWIQaPN2S4nOm4GfB/qHE+J5gUhmzs7b+p 6jKDLkAM1i7XEMUJIIMRWL7CX2DAPcBT8xGCFYV9hXg9E2cMYQHz9jYrxRuzi3cfQgoyV3 vi3Sg1V1QyLkCroQaD6tnOXdQw8TRbwhCkwLp0StGOfVO+eX0K3AinkGfLrIMNkFh3pAjm I7zow9ruKGain29v1HjJT3fH93BRcCQ4zdW0UMOsDpQzRdlcpZ2kU4IIWhRdYp+Q== Received: by filterdrecv-557d69979-tbkgw with SMTP id filterdrecv-557d69979-tbkgw-1-638BBD78-2B 2022-12-03 21:19:53.057099584 +0000 UTC m=+1376051.866357832 Received: from herokuapp.com (unknown) by geopod-ismtpd-4-6 (SG) with ESMTP id bxaSSpi7Qhm_m0GBxeVGew for ; Sat, 03 Dec 2022 21:19:52.910 +0000 (UTC) Date: Sat, 03 Dec 2022 21:19:53 +0000 (UTC) From: "Segaja (Andreas Schleifer)" 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-Sender: Segaja 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: 87535 X-SG-EID: =?us-ascii?Q?52aAbMi+wgaTIjiqmwFljYeAEr0ob8dcvFpVgqIqbJ8OmkxHNBL1dbrX0Y5vmg?= =?us-ascii?Q?3l9To1HI15ozhxLz8oHoKkrn+CyuZyfgsgAFwXu?= =?us-ascii?Q?0PxoDXZKqhx0tbtz9bWII0Gf5Zn6FYGam9LK=2FR8?= =?us-ascii?Q?BekS1s9qz2weLm1QZOPjgGhYuEgwQ6iyK9KIXzg?= =?us-ascii?Q?5Hq1j=2FiUHIPLEeKbgagJJMQvNJ=2FLRDFO8Y44O2K?= =?us-ascii?Q?0y0oneG+4e7NC2uTUcz3sT7I=2Ff2r7TXYGXGfco=2F?= =?us-ascii?Q?M294uF1VuwSJDNTo5fmFQ=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: GLOIBQA6KV465E3B6JBPRQLJSVJNBEIR X-Message-ID-Hash: GLOIBQA6KV465E3B6JBPRQLJSVJNBEIR 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:111183] [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 reported by Segaja (Andreas Schleifer). ---------------------------------------- Misc #19178: How does CRuby handle CVE issues in stdlib gems which get patched? https://bugs.ruby-lang.org/issues/19178 * Author: Segaja (Andreas Schleifer) * Status: Open * Priority: Normal ---------------------------------------- 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/