From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Siddhesh Poyarekar <sipoyare@redhat.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/5] SECURITY.txt changes
Date: Mon, 12 Oct 2026 14:49:09 +0100 [thread overview]
Message-ID: <cover.1791812758.git.aburgess@redhat.com> (raw)
Some changes to GDB's SECURITY.txt document. Patches #3 and #4 are
related, but all the others are standalone.
Feedback welcome.
Thanks,
Andrew
---
Andrew Burgess (5):
gdb: fix minor grammar error in SECURITY.txt
gdb: extend SECURITY.txt to highlight additional remote debugging
risks
gdb: extend SECURITY.txt discussion of DWARF/BFD parser bugs
gdb: in SECURITY.txt, add notes on reporting exec and debug bugs
gdb: improve SECURITY.txt relating to embedded language bugs
gdb/SECURITY.txt | 68 ++++++++++++++++++++++++++++++++----------------
1 file changed, 46 insertions(+), 22 deletions(-)
base-commit: 506d153ed46c3b5ffe9041647a9d57faae8ec22c
--
2.25.4
next reply other threads:[~2026-10-12 13:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:49 Andrew Burgess [this message]
2026-10-12 13:49 ` [PATCH 1/5] gdb: fix minor grammar error in SECURITY.txt Andrew Burgess
2026-10-14 15:02 ` Tom Tromey
2026-10-12 13:49 ` [PATCH 2/5] gdb: extend SECURITY.txt to highlight additional remote debugging risks Andrew Burgess
2026-10-13 15:22 ` Siddhesh Poyarekar
2026-10-14 15:08 ` Tom Tromey
2026-10-14 16:10 ` Siddhesh Poyarekar
2026-10-16 14:24 ` Andrew Burgess
2026-10-16 14:27 ` Siddhesh Poyarekar
2026-10-12 13:49 ` [PATCH 3/5] gdb: extend SECURITY.txt discussion of DWARF/BFD parser bugs Andrew Burgess
2026-10-13 15:30 ` Siddhesh Poyarekar
2026-10-14 15:12 ` Tom Tromey
2026-10-14 16:16 ` Siddhesh Poyarekar
2026-10-14 17:28 ` Carlos O'Donell
2026-10-12 13:49 ` [PATCH 4/5] gdb: in SECURITY.txt, add notes on reporting exec and debug bugs Andrew Burgess
2026-10-12 13:49 ` [PATCH 5/5] gdb: improve SECURITY.txt relating to embedded language bugs Andrew Burgess
2026-10-14 15:44 ` [PATCH 0/5] SECURITY.txt changes Tom Tromey
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=cover.1791812758.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sipoyare@redhat.com \
/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