From: Ian Lance Taylor <ian@airs.com>
To: Overseers <overseers@sourceware.org>
Subject: Re: Moving sourceware to the Linux Foundation? No thanks.
Date: Mon, 26 Sep 2022 07:07:20 -0700 [thread overview]
Message-ID: <m3mtamns9z.fsf@pepe.airs.com> (raw)
In-Reply-To: <YzDW3fJaw8NHFUwV@wildebeest.org> (Mark Wielaard via Overseers's message of "Mon, 26 Sep 2022 00:31:57 +0200")
I see two important points that ought to be discussed on this topic.
The first is succession planning. Sourceware is essentially a community
project with a relatively small number of people keeping it going. It
needs trusted and capable people to step it to continue to maintain it.
Where are those people going to come from? We shouldn't simply hope
that it will keep carrying on as before.
The second, mentioned in Mark's e-mail, is security. I hope that we can
all agree that there are highly intelligent, highly motivated people
seeking to break security on GNU/Linux and other free operating systems.
Years ago Ken Thompson laid out the roadmap for attacking an operating
system via the compiler and other code generation tools. These days
these are known as supply chain attacks. I think that the free software
community should reasonably insist that sourceware be defended against
these kinds of attacks with mechanisms for prevention and detection and
restoration. This is a hard job.
Ian
next prev parent reply other threads:[~2022-09-26 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yw5aTCLyYx8qqN3W@wildebeest.org>
2022-08-31 22:19 ` Proposing Sourceware as SFC member project Jose E. Marchesi
2022-09-01 8:28 ` Mark Wielaard
2022-09-02 18:51 ` Daniel Pono Takamori
2022-09-03 14:07 ` Karen M. Sandler
2022-09-03 16:38 ` Mark Wielaard
2022-09-18 19:42 ` Moving sourceware to the Linux Foundation? No thanks Christopher Faylor
2022-09-25 22:31 ` Mark Wielaard
2022-09-26 14:07 ` Ian Lance Taylor [this message]
2022-09-26 17:05 ` Christopher Faylor
2022-09-26 19:57 ` Frank Ch. Eigler
2022-09-27 13:03 ` Carlos O'Donell
2022-09-28 8:53 ` Ian Kelling
2022-10-02 21:15 ` Mark Wielaard
2022-09-28 8:33 ` Ian Kelling
2022-09-28 10:08 ` Frank Ch. Eigler
2022-09-26 21:53 ` Moving sourceware into the future Mark Wielaard
2022-09-27 17:12 ` Daniel Pono Takamori
2022-09-26 22:21 ` Moving sourceware to the Linux Foundation? No thanks Carlos O'Donell
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=m3mtamns9z.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=overseers@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).