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=-3.7 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS, UNPARSEABLE_RELAY shortcircuit=no autolearn=ham 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 BD2C51F601 for ; Sun, 4 Dec 2022 00:03:31 +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="QzRvKlbT"; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 6FE417E96F; Sun, 4 Dec 2022 00:03:24 +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=QzRvKlbT; dkim-atps=neutral Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 1B9577E95C for ; Sun, 4 Dec 2022 00:03:20 +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=6DgE4bRoRnZ1j+hTdZrwd3wR3oRnxfYN+g4rA4DPtOk=; b=QzRvKlbTUAgUYCZmhbQn8f6LYTcLEQuIzMEyl7ulmXqHbK3I/EUf4hbt79la1eyuul2K 0X906s7PTER3WUeMuVpFF5DuzqRhOmfhMom/O51WoNcFwfNJNFN8vQW80Jq6ftN2F+80Pr YB6LVMLGJB2T6vpvoLq8cdDAAOqtoTddq9Zg6arvWFkurmj47HRKZoALX9Nl3PXKGnJzYD GT/UW26UKg4QVK8+8aGnYRY4ge4zNllf+D2rOFzuaSBt79ciS1WU3BV9G+2tGWpQDctvIL 71m/bh3BUEqr8Nqkuv3s5lt6T81EemXz5iu1RZuI1wZt5wr8uN/Li/1US2Ie7T0A== Received: by filterdrecv-69c5db5cf4-msg49 with SMTP id filterdrecv-69c5db5cf4-msg49-1-638BE3C7-C 2022-12-04 00:03:19.463200185 +0000 UTC m=+1385714.792744292 Received: from herokuapp.com (unknown) by geopod-ismtpd-3-7 (SG) with ESMTP id vPaW4WVpTkGwEP1w4Bbplg for ; Sun, 04 Dec 2022 00:03:19.445 +0000 (UTC) Date: Sun, 04 Dec 2022 00:03:19 +0000 (UTC) From: "ioquatix (Samuel Williams)" 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: ioquatix 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: 87544 X-SG-EID: =?us-ascii?Q?RXGrw3WrKfUduNFRrzMMcXYHKEABJI9T84jNjq2g6rBTg=2FXhHIicnPoJUXLutJ?= =?us-ascii?Q?tdNFg7BiEDMUtMCwjaLtb0ItKeRyv3NlZm6AYiJ?= =?us-ascii?Q?s0JX4N8aAqzyz9=2Fz+Ot8+NcLWTxtftVa0JPOaS2?= =?us-ascii?Q?vSMSV9N59=2F4PxEPqRgo5Suz0HuX3vU0KBu2R5f0?= =?us-ascii?Q?0pWAa+vcBQUVgA5tcvNzGll6aQ2IrcuVBJFkw3J?= =?us-ascii?Q?Dk3uBFTxa+Vs9EWXwgKzznh3ZtamGSTY1MTkm3b?= =?us-ascii?Q?cbZ2P23H7ZkK1FGOxHO3w=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: DW3XW45AJWJOG4BCKWFFQIG3L7X5L42M X-Message-ID-Hash: DW3XW45AJWJOG4BCKWFFQIG3L7X5L42M 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:111192] [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 ioquatix (Samuel Williams). I've created an initial document, trying to distill some of the discussions here into a single place that downstream package maintainers can use as guidance. https://github.com/ruby/ruby/pull/6856 Please help expand this document to clarify various points about how Ruby itself should be distributed and the process around it. ---------------------------------------- Misc #19178: How does CRuby handle CVE issues in stdlib gems which get patched? https://bugs.ruby-lang.org/issues/19178#change-100476 * 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/