From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Paul Eggert <eggert@cs.ucla.edu>, libc-alpha@sourceware.org
Subject: Re: GNU C Library as its own CNA?
Date: Wed, 6 Sep 2023 07:41:54 -0400 [thread overview]
Message-ID: <d73ec14a-2b62-6f89-ac1b-fd927e712ed7@gotplt.org> (raw)
In-Reply-To: <6ad61af4-8890-809c-d168-5a6e8c750d26@cs.ucla.edu>
On 2023-07-28 13:28, Paul Eggert wrote:
> On 2023-07-28 09:41, Joseph Myers wrote:
>> If we add some kind of private submission
>> mechanism, we should also strongly discourage its use for the bulk of
>> low-risk issues to avoid adding unnecessary overhead for those.
>
> One possibility is to use an already-existing submission mechanism,
> namely the GNU Security Escalation Contact <security@gnu.org>. For what
> it's worth, that mailing list gets little email, mostly false alarms.
>
> https://savannah.gnu.org/mail/?group=security
Or alternatively, a private mailing list on sourceware alongside other
current lists. One of the future challenges may be to support encrypted
submissions since that seems to be a preference for some security
researchers. We could do that for now by just listing public keys of
volunteers in the security group but if we end up with too many such
submissions or have too many volunteers or otherwise have operational
difficulties then we may have to think of another solution.
Thanks,
Sid
next prev parent reply other threads:[~2023-09-06 11:41 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 [this message]
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
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=d73ec14a-2b62-6f89-ac1b-fd927e712ed7@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@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).