From: Carlos O'Donell via Gdb <gdb@sourceware.org>
To: 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>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Core Toolchain Infrastructure - October 2024 update
Date: Tue, 29 Oct 2024 18:02:03 -0400 [thread overview]
Message-ID: <9ee5b9e1-3f84-4d9e-8249-7a4bf8080bb0@redhat.com> (raw)
Core Toolchain Infrastructure - October 2024 update
The Core Toolchain Infrastructure (CTI) Project’s mission is to support
the GNU Toolchain community with secure infrastructure and state of the
art services required to support the community’s development efforts to
be a trusted foundation in a secure supply chain.
We want to keep the GNU Toolchain development community updated with the
latest information on the CTI project and how it can support the GNU
Toolchain.
Since 2022 [1][2] the CTI project has been working to carry out a
detailed enumeration of the services required by the projects and how
those services may be provided in a secure and robust fashion.
We have completed a detailed service enumeration for the GNU Toolchain:
https://cti.coretoolchain.dev/projects/enum.html
In 2024 we published updated project documentation:
https://cti.coretoolchain.dev
Also in 2024 we've looked at the details of the services we provide, why
we provide them, and how we might provide them with with increased
security and robustness, including putting together a statement of work
with the Linux Foundation Core IT team (who provides similar services to
the Linux Kernel) [3].
The CTI Technical Advisory Committee (TAC) is made up of members of the
development community of the projects, and is working on behalf of the
GNU Toolchain to improve security and robustness of the infrastructure
used by the community. The CTI TAC meets monthly and the meetings are
open for anyone to attend.
There is still a lot of work ahead of us to find a way forward to state
of the art sustainable secure and robust services for the GNU Toolchain
projects. Recent discussions on the glibc mailing list make it clear
that we need to expand and discuss more about our "why" along with
the "what" and "how" of these changes.
We will be sending out one of these updates every 3 months to all the
projects to keep you updated on our progress and discussions with the
GNU Toolchain projects and the wider
Sincerely,
Core Toolchain Infrastructure Technical Advisory Committee
[1] https://inbox.sourceware.org/overseers/ef140a6b-c72d-bd63-b94c-bceeb365b32a@redhat.com/
[2] https://inbox.sourceware.org/overseers/2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com/
[3] https://inbox.sourceware.org/libc-alpha/eb0d5e7b-0280-4c5a-aff6-3418a4210a39@redhat.com/
next reply other threads:[~2024-10-29 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:02 Carlos O'Donell via Gdb [this message]
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
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=9ee5b9e1-3f84-4d9e-8249-7a4bf8080bb0@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=libc-alpha@sourceware.org \
--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