From: Tom Tromey <tom@tromey.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Guinevere Larsen via Overseers <overseers@sourceware.org>,
Sandra Loosemore <sloosemore@baylibre.com>,
Mark Wielaard <mark@klomp.org>,
Guinevere Larsen <blarsen@redhat.com>,
gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
libc-alpha@sourceware.org
Subject: Re: Sourceware mitigating and preventing the next xz-backdoor
Date: Wed, 03 Apr 2024 08:04:59 -0600 [thread overview]
Message-ID: <87o7aq8ruc.fsf@tromey.com> (raw)
In-Reply-To: <87il0ykgw5.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Wed, 03 Apr 2024 10:08:26 +0200")
>>>>> "Florian" == Florian Weimer <fweimer@redhat.com> writes:
Florian> Everyone still pushes their own patches, and there are no
Florian> technical countermeasures in place to ensure that the pushed version is
Florian> the reviewed version.
This is a problem for gdb as well.
Probably we should switch to some kind of pull-request model, where
patches can only be landed via the UI, after sufficient review; and
where all generated files are regenerated by the robot before checkin.
(Or alternatively some CI runs and rejects patches where they don't
match.)
Tom
next prev parent reply other threads:[~2024-04-03 14:05 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 20:39 Security warning about xz library compromise Mark Wielaard
2024-04-01 15:06 ` Sourceware mitigating and preventing the next xz-backdoor Mark Wielaard
2024-04-02 19:54 ` Sandra Loosemore
2024-04-02 20:03 ` Paul Eggert
2024-04-02 20:20 ` Paul Koning via Gdb
2024-04-02 20:28 ` Ian Lance Taylor via Gdb
2024-04-03 6:26 ` Martin Uecker via Gdb
2024-04-03 14:00 ` Michael Matz via Gdb
2024-04-03 14:14 ` Paul Koning via Gdb
2024-04-03 14:32 ` Martin Uecker via Gdb
2024-04-03 14:46 ` Jeffrey Walton via Gdb
2024-04-03 14:56 ` Stephen Webb via Gdb
2024-04-06 13:09 ` Andrew Haley
2024-04-03 16:02 ` Michael Matz via Gdb
2024-04-03 16:26 ` Joel Sherrill
2024-04-03 16:32 ` Martin Uecker via Gdb
2024-04-03 16:51 ` Andreas Schwab
2024-04-03 16:56 ` Jonathan Wakely via Gdb
2024-04-03 18:46 ` Jonathon Anderson via Gdb
2024-04-03 19:01 ` Martin Uecker via Gdb
2024-04-05 21:15 ` Andrew Sutton via Gdb
2024-04-06 13:00 ` Richard Biener via Gdb
2024-04-06 15:59 ` Martin Uecker via Gdb
2024-04-04 13:59 ` Michael Matz via Gdb
2024-04-09 16:44 ` anderson.jonathonm--- via Gdb
2024-04-09 17:57 ` Andreas Schwab
2024-04-09 19:59 ` Jonathon Anderson via Gdb
2024-04-09 20:11 ` Paul Koning via Gdb
2024-04-09 21:40 ` Jeffrey Walton via Gdb
2024-04-09 21:50 ` Paul Eggert
2024-04-09 21:58 ` Sam James via Gdb
2024-04-09 22:15 ` Paul Eggert
2024-04-09 22:22 ` Sam James via Gdb
2024-04-09 22:53 ` Paul Eggert
2024-04-09 22:03 ` Jonathon Anderson via Gdb
2024-04-09 22:10 ` Sam James via Gdb
2024-04-09 21:54 ` Jonathon Anderson via Gdb
2024-04-09 22:00 ` Sam James via Gdb
2024-04-10 14:09 ` Frank Ch. Eigler via Gdb
2024-04-10 18:47 ` Jonathon Anderson via Gdb
2024-04-10 19:00 ` Frank Ch. Eigler via Gdb
2024-04-10 10:26 ` Claudio Bantaloukas via Gdb
2024-04-02 22:08 ` Guinevere Larsen via Gdb
2024-04-02 22:50 ` Jeffrey Walton via Gdb
2024-04-02 23:20 ` Mark Wielaard
2024-04-02 23:34 ` Paul Koning via Gdb
2024-04-03 0:37 ` Jeffrey Walton via Gdb
2024-04-03 8:08 ` Florian Weimer via Gdb
2024-04-03 13:53 ` Joel Sherrill
2024-04-04 10:25 ` Mark Wielaard
2024-04-10 16:30 ` Alejandro Colomar via Gdb
2024-04-21 15:30 ` Mark Wielaard
2024-04-21 20:40 ` Alejandro Colomar via Gdb
2024-04-21 20:52 ` Alejandro Colomar via Gdb
2024-04-30 11:28 ` Alejandro Colomar via Gdb
2024-04-03 14:04 ` Tom Tromey [this message]
2024-04-03 14:42 ` Jeff Law via Gdb
2024-04-04 10:48 ` Mark Wielaard
2024-07-13 13:56 Trenton Davison via Gdb
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=87o7aq8ruc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=blarsen@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=sloosemore@baylibre.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