From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, Alexandre Oliva <oliva@gnu.org>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: GNU C Library as its own CNA?
Date: Mon, 11 Sep 2023 08:59:03 -0400 [thread overview]
Message-ID: <391e524c-bf2a-56aa-027b-da98bbce83b3@redhat.com> (raw)
In-Reply-To: <87jzsx2lvl.fsf@oldenburg.str.redhat.com>
On 9/11/23 03:46, Florian Weimer wrote:
> * Alexandre Oliva:
>
>> On Sep 8, 2023, Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:
>>
>>> A single non-root CNA for all of the GNU project doesn't make sense to
>>> me, given that packages have very distinct communities and needs.
>>
>> It seem like you're saying that GNU, as a CNA, would be unable to offer
>> to individual packages whatever it is that Red Hat, as root CNA, would.
>> Could you please elaborate on that distinction you're making?
>
> I think we'd still want per-component CNAs, whether the GNU project is a
> (root) CNA or not.
Agreed. Per-component CNAs creates the least back-and-forth between the reporter and the
people who wrote the code and know how it works and the security policies for the
project.
> I suggest we start with Red Hat as the root CNA, get the glibc CNA set
> up. Once you have figured out the details with MITRE and the FSF and
> the GNU root is established, we can move over.
Agreed, this is the best first step IMO.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-09-11 12:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 15:56 Siddhesh Poyarekar
2023-07-28 16:09 ` Florian Weimer
2023-07-28 16:11 ` Siddhesh Poyarekar
2023-07-28 16:41 ` Joseph Myers
2023-07-28 17:28 ` Paul Eggert
2023-09-06 11:41 ` Siddhesh Poyarekar
2023-09-06 12:33 ` Florian Weimer
2023-09-06 16:00 ` Paul Eggert
2023-09-06 16:33 ` Florian Weimer
2023-09-06 17:04 ` Paul Eggert
2023-07-31 17:42 ` Siddhesh Poyarekar
2023-09-06 11:40 ` Siddhesh Poyarekar
2023-09-06 18:35 ` Alexandre Oliva
2023-09-06 18:57 ` Siddhesh Poyarekar
2023-09-06 19:02 ` Paul Eggert
2023-09-06 22:01 ` Alexandre Oliva
2023-09-07 0:56 ` Siddhesh Poyarekar
2023-09-07 3:27 ` Alexandre Oliva
2023-09-07 10:48 ` Siddhesh Poyarekar
2023-09-07 15:46 ` Florian Weimer
2023-09-07 17:14 ` Alexandre Oliva
2023-09-08 10:58 ` Siddhesh Poyarekar
2023-09-10 16:57 ` Alexandre Oliva
2023-09-11 7:46 ` Florian Weimer
2023-09-11 12:59 ` Carlos O'Donell [this message]
2023-09-11 9:58 ` Siddhesh Poyarekar
2023-09-11 12:47 ` Carlos O'Donell
2023-09-12 11:40 ` Siddhesh Poyarekar
2023-09-12 13:15 ` Adhemerval Zanella Netto
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=391e524c-bf2a-56aa-027b-da98bbce83b3@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=oliva@gnu.org \
--cc=siddhesh@gotplt.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).