From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: What is our SLA for going from reserved CVE to published CVE?
Date: Thu, 02 May 2024 00:06:20 -0400 [thread overview]
Message-ID: <xnfrv026yr.fsf@greed.delorie.com> (raw)
In-Reply-To: <ab1df515-18fa-4d2b-836b-543da608ded3@redhat.com> (carlos@redhat.com)
"Carlos O'Donell" <carlos@redhat.com> writes:
> Would it be better if we just published interm text and updated as we go?
Putting on my "generic user" hat...
The point of a CVE is to let users know, as quickly as possible:
1. What happened
2. What, if anything, they need to do IMMEDIATELY
3. What the long-term solution would be
I think if you have some but not all of these, at least in the correct
order, publishing what you know and updating it later would be far
better than waiting - and letting the user be compromised - for a full
report later. Especially if you have 1+2 but are waiting on 3.
So in the non-embargo case, I advocate for giving out information as we
have it. It's better for the user and more in line with our "open"
philosophy.
next prev parent reply other threads:[~2024-05-02 4:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 2:12 Carlos O'Donell
2024-05-02 4:06 ` DJ Delorie [this message]
2024-05-02 10:35 ` Siddhesh Poyarekar
2024-05-02 10:46 ` Florian Weimer
2024-05-15 18:32 ` Carlos O'Donell
2024-05-15 18:36 ` Siddhesh Poyarekar
2024-05-16 7:21 ` Adhemerval Zanella Netto
2024-05-16 11:16 ` 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=xnfrv026yr.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--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).