From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] manuals: initial documentation for CVE management
Date: Fri, 30 Jul 2021 20:59:59 +0200 [thread overview]
Message-ID: <44a78110-7108-c12b-d0c2-468eb1fe32b1@bootlin.com> (raw)
In-Reply-To: <1696A6679AD2D10A.1941@lists.yoctoproject.org>
Greetings,
On 7/30/21 8:54 PM, Michael Opdenacker wrote:
> This starts to document vulnerability management
> and the use of the CVE_PRODUCT variable
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
> documentation/dev-manual/common-tasks.rst | 46 +++++++++++++++++++++++
> documentation/ref-manual/variables.rst | 11 ++++++
> 2 files changed, 57 insertions(+)
In addition to your reviews of this particular text, I'm also interested
in further guidelines for managing CVEs in production projects.
I already asked such questions in
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14419:
* How to check for vulnerabilities in my image without regenerating
it, and without runing "bitbake -c cve_check" on individual package
names?
* How to check production images for vulnerability checks? Anything
better than manual or cronjob checks?
Thank you in advance for your advise for our readers!
Cheers,
Michael
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2021-07-30 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1696A6679AD2D10A.1941@lists.yoctoproject.org>
2021-07-30 18:59 ` Michael Opdenacker [this message]
2021-07-30 18:54 [PATCH] manuals: initial documentation for CVE management Michael Opdenacker
2021-08-02 9:36 ` [docs] " Quentin Schulz
2021-08-02 14:49 ` Michael Opdenacker
2021-08-02 14:59 ` 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=44a78110-7108-c12b-d0c2-468eb1fe32b1@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.