From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id CO3rNJrjNmQQ3ykAWB0awg (envelope-from ) for ; Wed, 12 Apr 2023 13:00:10 -0400 Received: by simark.ca (Postfix, from userid 112) id C59ED1E221; Wed, 12 Apr 2023 13:00:10 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=goXw0Rm0; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 6D51F1E0D3 for ; Wed, 12 Apr 2023 13:00:10 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 8BCA63857737 for ; Wed, 12 Apr 2023 17:00:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8BCA63857737 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681318808; bh=ehOxAiJlVNYfD2vdJhdpzCtnRsd7OfJ+nZo5GgIOHRc=; h=Subject:In-Reply-To:Date:Cc:References:To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=goXw0Rm0RRxSPwC8BdD5e4VxWWTfoJWQubnhrsifxkoIIE1IVGAKYLYdCaiKMmWWC Mju5DidyCj7O9SlVaJ+40mS/i+SGrpCdpukXJOVqpvasJmR/7gMWk0FWxvQZwRsC2K 2abu3UfZkHg2Zhku0Esn3gJzg1Dqn1mSv6sBwN7U= Received: from resqmta-c1p-024061.sys.comcast.net (resqmta-c1p-024061.sys.comcast.net [IPv6:2001:558:fd00:56::6]) by sourceware.org (Postfix) with ESMTPS id BE22C385842D for ; Wed, 12 Apr 2023 16:58:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BE22C385842D Received: from resomta-c1p-023810.sys.comcast.net ([96.102.18.241]) by resqmta-c1p-024061.sys.comcast.net with ESMTP id mddPpSQrdGE7KmdntpI9zr; Wed, 12 Apr 2023 16:58:41 +0000 Received: from smtpclient.apple ([73.60.223.101]) by resomta-c1p-023810.sys.comcast.net with ESMTPSA id mdnrp5qVEa62tmdnspD7vM; Wed, 12 Apr 2023 16:58:41 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvhedrvdekiedguddtlecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjffevgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheprfgruhhlucfmohhnihhnghcuoehprghulhhkohhnihhnghestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepveekveelffeliefgiedufeehgeejtdfhgedujeehueekiedtgfetffevgffggfdvnecukfhppeejfedriedtrddvvdefrddutddunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohepshhmthhptghlihgvnhhtrdgrphhplhgvpdhinhgvthepjeefrdeitddrvddvfedruddtuddpmhgrihhlfhhrohhmpehprghulhhkohhnihhnghestghomhgtrghsthdrnhgvthdpnhgspghrtghpthhtohephedprhgtphhtthhopehrihgthhgrrhgurdgvrghrnhhshhgrfiesfhhoshhsrdgrrhhmrdgtohhmpdhrtghpthhtohepshhiugguhhgvshhhsehgohhtphhlthdrohhrghdprhgtphhtthhopehnihgtkhgtsehrvgguhhgrthdrtghomhdprhgtphhtthhopegsihhnuhhtihhlshesshhouhhrtggvfigrrhgvrdhorhhgpdhrtghpthhtohepghgusgesshhouhhrtggvfigrrhgvrdhorhhg X-Xfinity-VMeta: sc=-100.00;st=legit Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: RFC: Adding a SECURITY.md document to the Binutils In-Reply-To: Date: Wed, 12 Apr 2023 12:58:39 -0400 Cc: Siddhesh Poyarekar , Nick Clifton , Binutils , "gdb@sourceware.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3A484AE1-77A9-47F4-A4F4-E8C5A333DB7C@comcast.net> References: <1c38b926-e003-0e21-e7f1-3d5dbec2aabf@redhat.com> <5b147005-bd28-4cf9-b9e7-479ef02cb1ad@foss.arm.com> <5d044987-39eb-a060-1b2b-9d07b1515e7d@gotplt.org> To: Richard Earnshaw X-Mailer: Apple Mail (2.3696.120.41.1.3) X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Paul Koning via Gdb Reply-To: Paul Koning Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" > On Apr 12, 2023, at 12:52 PM, Richard Earnshaw via Gdb = wrote: >=20 > On 12/04/2023 17:26, Siddhesh Poyarekar wrote: >> ... >> Ack, I reckon this should be addressed by "corrupt output files from = valid trusted inputs". If that's not clear enough, could you suggest = alternative phrasing that makes it clearer? >=20 > I'm not sure corrupt is general enough. Each instruction in the = binary might be completely legal, but their sequencing could leave some = vulnerabilities (think spectre, for example, but that's pretty extreme). >=20 > Perhaps something like "... this means that the tools introduce a = vulnerability in the output file that was not present in the input files = being processed". I think with that wording you probably don't even = need the last sentence in the first paragraph. I agree. The scenario in "Reflections on trusting trust", Ken = Thompson's famous paper, comes to mind. It might be worth adding that = as a reference. paul