Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: Andrew Burgess <aburgess@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Siddhesh Poyarekar <siddhesh@redhat.com>,
	Kevin Buettner <kevinb@redhat.com>,
	Simon Marchi <simark@simark.ca>,
	Paul Koning <paulkoning@comcast.net>
Subject: RE: [V5] [RFC] Adding a SECURITY policy for GDB
Date: Wed, 10 Apr 2024 10:22:05 +0000	[thread overview]
Message-ID: <MN2PR11MB4566576CBCACFC6ADEA91E928E062@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87r0fg15kd.fsf@redhat.com>

> -----Original Message-----
> From: Andrew Burgess <aburgess@redhat.com>
> Sent: Montag, 8. April 2024 13:02
> To: gdb-patches@sourceware.org
> Cc: Siddhesh Poyarekar <siddhesh@redhat.com>; Kevin Buettner
> <kevinb@redhat.com>; Simon Marchi <simark@simark.ca>; Willgerodt, Felix
> <felix.willgerodt@intel.com>; Paul Koning <paulkoning@comcast.net>
> 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.

Regards,
Felix


> Reporting Security Bugs
> -----------------------
> 
>   In order to report a private security bug that is not immediately
>   made public, please contact one of the downstream distributions with
>   security teams.  The following teams have volunteered to handle such
>   bugs:
> 
>      Red Hat: secalert@redhat.com
>      SUSE:    security@suse.de
> 

In case you wanted to align the two email addresses, they aren't quite
aligned.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  parent reply	other threads:[~2024-04-10 10:22 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 [this message]
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

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=MN2PR11MB4566576CBCACFC6ADEA91E928E062@MN2PR11MB4566.namprd11.prod.outlook.com \
    --to=felix.willgerodt@intel.com \
    --cc=aburgess@redhat.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