From: Gordon Pettey <petteyg359@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] A new GLSA schema
Date: Fri, 11 Nov 2022 18:04:31 -0600 [thread overview]
Message-ID: <CAHY5MecH5hp_1uBgRQLGZK30tMciA-nP6vubxwnZ3kkCRqz6AQ@mail.gmail.com> (raw)
In-Reply-To: <018B23C1-7F65-4D99-A2E0-03B5280918FC@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
On Fri, Nov 11, 2022 at 4:43 PM Sam James <sam@gentoo.org> wrote:
>
> Oh I see, I'd missed the actual link to CSAF, sorry.
>
> I'll take a look. It's not clear to me yet if this is going to be a good
> fit for distributions though, as we're not a normal "vendor".
>
> Are you aware of any other Linux distros using this?
>
Red Hat has it in "beta": https://access.redhat.com/security/data, and has
had the prior OASIS format (CVRF) for a time, which they (Red Hat) will be
deprecating in 2023-01. There is also VEX, which is (I think, didn't read
the detailed spec) a subset of CSAF.
[-- Attachment #2: Type: text/html, Size: 1009 bytes --]
next prev parent reply other threads:[~2022-11-12 0:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 2:27 [gentoo-dev] [RFC] A new GLSA schema John Helmert III
2022-11-10 3:43 ` Michał Górny
2022-11-10 3:58 ` Sam James
2022-11-10 4:10 ` Marc Schiffbauer
2022-11-10 4:19 ` John Helmert III
2022-11-10 6:46 ` Marc Schiffbauer
2022-11-10 4:13 ` John Helmert III
2022-11-10 8:43 ` Jaco Kroon
2022-11-10 9:40 ` Matthew Smith
2022-11-10 9:48 ` Jaco Kroon
2022-11-10 10:19 ` Sam James
2022-11-10 10:51 ` Jaco Kroon
2022-11-10 14:24 ` John Helmert III
2022-11-10 20:07 ` Jaco Kroon
2022-11-10 20:55 ` Mart Raudsepp
2022-11-11 0:22 ` John Helmert III
2022-11-10 20:49 ` Jonas Stein
2022-11-11 0:27 ` John Helmert III
2022-11-11 22:06 ` Gordon Pettey
2022-11-11 22:40 ` Sam James
2022-11-11 22:43 ` Sam James
2022-11-12 0:01 ` Jonas Stein
2022-11-12 0:03 ` Sam James
2022-11-12 13:15 ` Jonas Stein
2022-11-12 0:04 ` Gordon Pettey [this message]
2022-11-12 0:06 ` Sam James
2022-11-12 5:09 ` Michał Górny
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=CAHY5MecH5hp_1uBgRQLGZK30tMciA-nP6vubxwnZ3kkCRqz6AQ@mail.gmail.com \
--to=petteyg359@gmail.com \
--cc=gentoo-dev@lists.gentoo.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