From: Joseph Myers via Gdb <gdb@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "Mark Wielaard" <mark@klomp.org>,
"gcc developers" <gcc@gcc.gnu.org>,
"glibc developers" <libc-alpha@sourceware.org>,
"gdb developers" <gdb@sourceware.org>,
"binutils developers" <binutils@sourceware.org>,
"Overseers mailing list" <overseers@sourceware.org>,
cti-tac@lists.linuxfoundation.org, "Zoë Kooyman" <zoe@fsf.org>,
"Karen M. Sandler" <karen@sfconservancy.org>
Subject: Re: Core Toolchain Infrastructure - October 2024 update
Date: Wed, 30 Oct 2024 17:06:54 +0000 (UTC) [thread overview]
Message-ID: <94813230-3ceb-8060-4272-57612b65cfb1@redhat.com> (raw)
In-Reply-To: <5691d7c8-f92e-46f3-8edf-c83e085dbfa2@redhat.com>
On Wed, 30 Oct 2024, Carlos O'Donell via Gcc wrote:
> Have you broken down those project goals into actionable steps that
> could be taken?
>
> For example filing Sourceware Infrastructure bugs for each service that
> needs to be migrated into a VM and isolated (with a top level tracker
> for "Increased isolation")?
Note that we have the CTI service enumeration which effectively identifies
the various services that should be isolated for various GNU toolchain
projects.
There may be other services on Sourceware that aren't used by any of the
GNU toolchain projects with CTI service enumerations. Those can still be
of security relevance to the toolchain, if a compromise of one of those
services could be leveraged to compromise other services or projects -
isolation matters both inward and outward, for both current and future
services and projects.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-10-30 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:02 Carlos O'Donell via Gdb
2024-10-30 10:39 ` Mark Wielaard
2024-10-30 12:32 ` Carlos O'Donell via Gdb
2024-10-30 15:45 ` Mark Wielaard
2024-10-30 16:23 ` Karen M. Sandler via Gdb
2024-10-30 16:45 ` Joseph Myers via Gdb
2024-10-30 16:52 ` Carlos O'Donell via Gdb
2024-10-30 17:06 ` Joseph Myers via Gdb [this message]
2024-11-04 10:50 ` Mark Wielaard
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=94813230-3ceb-8060-4272-57612b65cfb1@redhat.com \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=gcc@gcc.gnu.org \
--cc=josmyers@redhat.com \
--cc=karen@sfconservancy.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=zoe@fsf.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