From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
libc-alpha@sourceware.org <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: What is our SLA for going from reserved CVE to published CVE?
Date: Thu, 02 May 2024 12:46:41 +0200 [thread overview]
Message-ID: <87wmoclcdq.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <c28451e4-335f-4a79-90b4-52f3c993ba78@redhat.com> (Siddhesh Poyarekar's message of "Thu, 2 May 2024 06:35:44 -0400")
* Siddhesh Poyarekar:
> On 2024-05-01 22:12, Carlos O'Donell wrote:
>> Would it be better if we just published interm text and updated as
>> we go?
>
> The CVE record tends to have a single line description that identifies
> affected functionality and versions, which I think we should be able
> to deliver when we reserve the CVE.
I think this would be best, yes.
> One thing I haven't tested yet is the feature to publish records at a
> specific future date. If that works, we could make it part of our
> workflow to add a description at the time of CVE number reservation,
> regardless of embargo state.
It may make things more complicated because you have to remember to
adjust the pending publication data whenever things evolve during the
embargo phase. The time-based publication also seems a bit scary.
Thanks,
Florian
next prev parent reply other threads:[~2024-05-02 10:46 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
2024-05-02 10:35 ` Siddhesh Poyarekar
2024-05-02 10:46 ` Florian Weimer [this message]
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=87wmoclcdq.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@redhat.com \
/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).