From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id mKnpH/PLK2aK8DwAWB0awg (envelope-from ) for ; Fri, 26 Apr 2024 11:44:51 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=dV2ue6bt; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 7DF271E0C1; Fri, 26 Apr 2024 11:44:51 -0400 (EDT) Received: from server2.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 ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 64F971E092 for ; Fri, 26 Apr 2024 11:44:49 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 0E29F385840A for ; Fri, 26 Apr 2024 15:44:49 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 400133858C42 for ; Fri, 26 Apr 2024 15:44:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 400133858C42 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 400133858C42 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714146270; cv=none; b=DPclRqjAn9WisfMYxtFa6b/26Y+LIpP6JrmPjbCoVdAz1+eyFUqSMZe8oaK/ZHsiHJip9jbd027ax8qIrkHRW+uIeztL0viRwxH99oicTO7CReHtthO4cFwdZLKNE53uo7RIz3htmIgEfXLtcNfrGaAcCpeq4VCXQCLQo6Cl6X0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714146270; c=relaxed/simple; bh=nQsXsvAiWS88dvj5uC0o2L2t4trzygAL1jISLnhQvkQ=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=Pq3WcuUvfnyK0RpE2V9Xrm+DW83UBZ1a94RV9/zYDirxXNu0vlzemyXcTa9s9REkBQucL1Dc8EVMYtfqsP0kq1dl3Z6R25+Kk2Ve8+wRAti886UJoDUFbjgUUYs74lh5lsyGhRBNuxQBTdMdmeDjE5RWDZDue4FoQdypYJlAlt4= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1714146265; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=YPbBO/AaxqiI+8dRXxyqmkEu21zYEuyZtxZJcZwZ4m4=; b=dV2ue6btDv5rD73kQs07njqSv8FvdS9GPHmIJpBgNXK74Y2CdIdjbA1JWG05DEdH7Km2ya UOuV+t3vD6TPzi+daceKqdFvcWMm+Bc1eU1eeq4OMCiWYbWDDILK76YIxXmv2XVBZD2DdE o/Kr4XKNhH4cVR/7hOfOBrxWEGn6jb4= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-493-8b18GmWpOMm9ZhXhnallKA-1; Fri, 26 Apr 2024 11:44:24 -0400 X-MC-Unique: 8b18GmWpOMm9ZhXhnallKA-1 Received: by mail-wm1-f69.google.com with SMTP id 5b1f17b1804b1-41552c04845so11331895e9.2 for ; Fri, 26 Apr 2024 08:44:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714146263; x=1714751063; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YPbBO/AaxqiI+8dRXxyqmkEu21zYEuyZtxZJcZwZ4m4=; b=TT7nUdEdLZPjUeRCn31MGrMyeYUzGZYgaNfj4J0H+vmr0umky88CWWOcQ9SDt95f29 ICT89XMGUCuEjRNOODgWIV3JTGPxLU6/M0GRyO9ps0Z9mKec+cn1d5K+2+GrGGvwCCk/ ne5kSW0DamEneBMKAAPbsi0OsGpiHJBQS9p9yrGaVmMc0CKuzOXbQdp+nsyvyHAYTyPa FUfCl7okp8+o5SvS9Xe/suqSIMUWBCDvEsGITD3+tKzjWv+vGEAihDLn/mcOYZ+ZDPCc RLSnBSXmkEzbfAMZ9iz9blxQgrxjDTEwDcTc7ufl8MsGUdKh40ZUXpi4BQP/RmpbkU5C pvBw== X-Forwarded-Encrypted: i=1; AJvYcCWECvn841Qg5ytRS48/RKeJblumuRTnigMRYRPefT+t6sxTKPINOvWa29T0j3ZP+ak1OUgg4FD/7uUZWHH+Nolj9B8NqplVNTEB6A== X-Gm-Message-State: AOJu0Yz3wdeI1RAImA4DUaJout+TKwlievjFlS6wqGK3+j7FlwGJOAU5 w7o30z3APW+HkzdmuuPSpX6oqIjb0ooO7Xg5zEbPKcE1UqjEAxzJUyHuYPWP4vognl8NPPfA1Eh upwDuoEJeovn/ATIIssBaOAhtMSjVMyAQ9AwN1mJJE2RkxLAHm8NWbmtPrmRRyY4qz+Y= X-Received: by 2002:a05:600c:4e87:b0:414:273:67d4 with SMTP id f7-20020a05600c4e8700b00414027367d4mr2261110wmq.30.1714146263106; Fri, 26 Apr 2024 08:44:23 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGo51brjSJvUpWNxfrTMBeukc1SsBDh41h7RY3VmuIH3XQ66CbLzfV0YTrFY9IcqesuLHT8rg== X-Received: by 2002:a05:600c:4e87:b0:414:273:67d4 with SMTP id f7-20020a05600c4e8700b00414027367d4mr2261084wmq.30.1714146262522; Fri, 26 Apr 2024 08:44:22 -0700 (PDT) Received: from localhost (185.223.159.143.dyn.plus.net. [143.159.223.185]) by smtp.gmail.com with ESMTPSA id q15-20020a05600c46cf00b00416e2c8b290sm35346744wmo.1.2024.04.26.08.44.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Apr 2024 08:44:22 -0700 (PDT) From: Andrew Burgess To: "Willgerodt, Felix" , "gdb-patches@sourceware.org" Cc: Siddhesh Poyarekar , Kevin Buettner , Simon Marchi , Paul Koning Subject: RE: [V5] [RFC] Adding a SECURITY policy for GDB In-Reply-To: References: <877cmvui64.fsf@redhat.com> <87wmtog2f4.fsf@redhat.com> <874jeo5jip.fsf@redhat.com> <87o7cd6fmk.fsf@redhat.com> <87msqk3pnt.fsf@redhat.com> <87r0fg15kd.fsf@redhat.com> Date: Fri, 26 Apr 2024 16:44:21 +0100 Message-ID: <877cgkt9gq.fsf@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org "Willgerodt, Felix" writes: >> -----Original Message----- >> From: Andrew Burgess >> Sent: Montag, 8. April 2024 13:02 >> To: gdb-patches@sourceware.org >> Cc: Siddhesh Poyarekar ; Kevin Buettner >> ; Simon Marchi ; Willgerodt, Felix >> ; Paul Koning >> Subject: [V5] [RFC] Adding a SECURITY policy for GDB >> >> >> In V5: >> >> - Fixed a couple of minor typos that were pointed out by someone >> off-list. >> >> Any additional feedback would be great. >> >> If there's no feedback, how would people feel about me merging this? So >> long as the content is not objectionable then minor corrections or >> additions can be made via the normal patch process in the future. >> >> I know I mentioned adding this text to the GDB manual previously, but I >> recall someone objected to that at the time. Right now I'm thinking to >> add this as a standalone document, and possibly merge it into the manual >> later in the year. >> >> Thoughts? >> >> Thanks, >> Andrew > > I find the text reasonable and am in favour of merging this and evolving it > from there if needed. > > Having a SECURITY file in repos seems common practice nowadays. > Though having it in the manual also has its advantages, as there it is potentially > easier to find for users. Maybe we could reference the docs from the > SECURITY file? But I am ok with either places, having it at all is most > important. Hi Felix, I'm also think having this text in the manual might be a good thing. When I mentioned this idea earlier in the thread there was some disagreement though, so for now I've merged this as a text file; I'm keen to get something in to the tree, then I can potentially move it later on. I'll work up a patch to move this into the manual and post it probably after 15.1 branches. Thanks, Andrew