From: Marta Rybczynska <rybczynska@gmail.com>
To: YP docs mailing list <docs@lists.yoctoproject.org>,
yocto-security@lists.yoctoproject.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: Documenting security advisories
Date: Mon, 18 Dec 2023 16:37:53 +0100 [thread overview]
Message-ID: <CAApg2=RSBvoPrS4F5ZOxtwEN97188huhA0LSQ_WXT3vocarb5g@mail.gmail.com> (raw)
Hello,
When discussing security processes, there is one thing that we haven't
set up for now. This is, where are we going to put any possible
security advisories affecting the Yocto Project. The need to release
such an advisory could happen one day.
A security advisory describes in more detail a single issue or a
series of issues. Gives the context, workarounds, information about
the version where the issue is fixed. An issue from an advisory is
likely affecting multiple versions of YP, and might have different
fixes for each version. The advisory will be referenced in the CVE
issue, security aggregators etc.
Where can we put such advisories:
* mailing list of the affected layer/module
* general documentation in "Release Manuals", using a separate section
for advisories with links from each of the affected versions? OR a
separate manual section?
What do you think?
Kind regards,
Marta
next reply other threads:[~2023-12-18 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:37 Marta Rybczynska [this message]
[not found] ` <a4b99195-4cf4-4392-b8be-43357fb22002@kernel.crashing.org>
2023-12-19 10:00 ` [yocto-security] Documenting security advisories Michael Opdenacker
2023-12-19 10:25 ` [docs] " Richard Purdie
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='CAApg2=RSBvoPrS4F5ZOxtwEN97188huhA0LSQ_WXT3vocarb5g@mail.gmail.com' \
--to=rybczynska@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto-security@lists.yoctoproject.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).