Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>,
	Guinevere Larsen <blarsen@redhat.com>,
	gdb-patches@sourceware.org
Cc: Kevin Buettner <kevinb@redhat.com>,
	Simon Marchi <simark@simark.ca>,
	felix.willgerodt@intel.com, Paul Koning <paulkoning@comcast.net>
Subject: Re: [RFC] Adding a SECURITY policy for GDB
Date: Wed, 14 Feb 2024 15:03:16 +0000	[thread overview]
Message-ID: <87r0hf5brf.fsf@redhat.com> (raw)
In-Reply-To: <f6ac80b8-96d1-486d-a14d-c157a51a22dc@redhat.com>

Siddhesh Poyarekar <siddhesh@redhat.com> writes:

> On 2024-02-12 11:43, Guinevere Larsen wrote:
>> On 08/12/2023 16:05, Andrew Burgess wrote:
>>> One last thing, while writing this, I did wonder if this text would be
>>> better moved into the GDB manual, and the gdb/SECURITY.txt document
>>> should just say "See the GDB manual", but I figure that's a problem for
>>> future me, for now I just need to find some words we can all agree on.
>>>
>>> Thanks,
>>> Andrew
>> 
>> Would it be possible to do the opposite and have the docs pull from the 
>> txt document? I like the idea of having specific files that are easy to 
>> check as a developer or end user, and I think having a file that says 
>> "look at that other file" that contains everything GDB (and thus makes 
>> it harder to quickly find what you're looking for) would muddle that a 
>> little bit.
>
> Not to mention the fact that $topsrcdir/SECURITY* is the first place 
> where people tend to look to report potential security issues.  This is 
> similar in principle to "Reporting bugs"; the manual is usually the last 
> place one would look, although it makes sense to *also* put it in the 
> manual.
>

Which is why the SECURITY* file would redirect to the definitive text.

But this feels like a future problem.  First we need to reach consensus
on some actual words.

Thanks,
Andrew


      reply	other threads:[~2024-02-14 15:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 13:26 Andrew Burgess
2023-11-06 18:55 ` Kevin Buettner
2023-11-06 19:34 ` Simon Marchi
2023-11-06 20:09   ` Siddhesh Poyarekar
2023-11-06 20:15     ` Simon Marchi
2023-11-07 12:17       ` Siddhesh Poyarekar
2023-11-07 14:22         ` Simon Marchi
2023-11-09 14:35   ` Willgerodt, Felix
2023-11-16 17:19   ` Andrew Burgess
2023-11-16 17:27     ` Paul Koning
2023-11-16 21:35       ` Siddhesh Poyarekar
2023-12-08 15:05 ` Andrew Burgess
2023-12-09 10:55   ` Eli Zaretskii
2024-02-04 15:32     ` Andrew Burgess
2024-02-04 17:18       ` Eli Zaretskii
2024-02-04 17:43         ` Andreas Schwab
2024-02-04 18:56           ` Eli Zaretskii
2024-02-05 11:06         ` Andrew Burgess
2023-12-12  7:27   ` Willgerodt, Felix
2024-02-04 15:36   ` [V3] " Andrew Burgess
2024-02-18 13:55     ` Andrew Burgess
2024-03-27 11:00       ` [V4] " Andrew Burgess
2024-04-08 11:01         ` [V5] " Andrew Burgess
2024-04-09 20:30           ` Tom Tromey
2024-04-10 10:22           ` Willgerodt, Felix
2024-04-26 15:44             ` Andrew Burgess
2024-02-05 21:01   ` Tom Tromey
2024-02-09 15:59     ` Andrew Burgess
2024-02-12 16:43   ` Guinevere Larsen
2024-02-12 17:06     ` Siddhesh Poyarekar
2024-02-14 15:03       ` Andrew Burgess [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0hf5brf.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=blarsen@redhat.com \
    --cc=felix.willgerodt@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=paulkoning@comcast.net \
    --cc=siddhesh@redhat.com \
    --cc=simark@simark.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox