summaryrefslogtreecommitdiffstats
path: root/documentation/figures
diff options
context:
space:
mode:
authorAntonin Godard <antonin.godard@bootlin.com>2025-12-04 16:23:05 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2026-01-26 09:41:30 +0000
commit9b6d0d6e5af8fb39c455b7fadeb18aa154c2ed13 (patch)
tree15f9ef827a19f9720c85fba497405c3ddc5aa662 /documentation/figures
parent495e1c2ed0e963a2fe27259086e72fd9a3c675da (diff)
downloadpoky-9b6d0d6e5af8fb39c455b7fadeb18aa154c2ed13.tar.gz
Add a new "Security" section
The current security-related documentation is a bit hard to find and hidden within the development manual. However these are processes that are not part of a development task but is rather a vulnerability reporting process. Create a new "Security" section in the documentation to gather this information. This will be directly visible in the sidebar when opening the documentation. Split the previous security-subjects.rst document into 2 documents: - security-team.rst: defines the roles of the security teams and its members. - reporting-vulnerabilities.rst: guide to report vulnerabilities to the security team. The plan is to backport these documents to active releases. As a consequence, this section should be free of instructions and information that only make sense for a specific release. It should _not_ contain documents on how to enable security features with Yocto on target devices, this is unrelated and can be left in the development manual (for example: dev-manual/vulnerabilities.rst to deal with CVEs). (From yocto-docs rev: 80556704f8b60b5bf903da497909cfda7dd1b28b) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> (cherry picked from commit 81e14ca2d5cff9e2104c556655144b069633790c) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/figures')
0 files changed, 0 insertions, 0 deletions