From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>
Cc: "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: Wed, 15 May 2024 14:36:31 -0400 [thread overview]
Message-ID: <a8041287-b824-47ba-ad2c-0a1475e3d45a@redhat.com> (raw)
In-Reply-To: <211c125f-ce39-419f-a229-1675dc7e8125@redhat.com>
On 2024-05-15 14:32, Carlos O'Donell wrote:
> On 5/2/24 6:46 AM, Florian Weimer wrote:
>> * 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.
>
> Just for clarity, reservation does not require any updates.
>
> I would have to *publish* the CVE IDs with *minimal* data to meet the CNA rules.
>
> This includes having a valid public link, which means I need to also commit minimal
> text to the advisories/ directory for the link to be valid.
>
> Are we agreeing to a minimal publishing regime followed by an update?
>
Yes.
Sid
next prev parent reply other threads:[~2024-05-15 18:36 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
2024-05-15 18:32 ` Carlos O'Donell
2024-05-15 18:36 ` Siddhesh Poyarekar [this message]
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=a8041287-b824-47ba-ad2c-0a1475e3d45a@redhat.com \
--to=siddhesh@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@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).