| Summary: | Add security configuration documentation | ||
|---|---|---|---|
| Product: | [Documentation] Development Manual | Reporter: | Michael Opdenacker <michael.opdenacker> |
| Component: | development | Assignee: | Antonin Godard <antonin.godard> |
| Status: | IN PROGRESS DOCUMENTATION --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | akuster808, ccasciato, michael.opdenacker, randy.macleod, richard.purdie, tim.orling |
| Version: | 3.3 | ||
| Target Milestone: | 6.2 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Michael Opdenacker
2021-08-13 10:27:28 UTC
Bulk move of 5.1 M4 to 5.2 M2 as approved by AlexB. Bulk move of bugs I am assigned to from Milestone 5.2M4 to 5.3M1. I sent a patch to create "security manual" (the name was chosen this way to resemble other sections of the docs, such the reference manual, development task manual, etc.). https://lore.kernel.org/r/20260106-security-manual-v1-0-500fe611a4d0@bootlin.com To give an update, the above patch was merged, and we now have a dedicated section in the documentation for this: https://docs.yoctoproject.org/security-manual/index.html The intent is to document security practices here, beginning with what we already had in the documentation, gathered here. Now, creating a "security configuration" document is a good idea, but the scope of it is large, so I'd say we limit this section to what is actively maintained in OE-Core. Is there anything else we can document in this section that is supported by OE-Core? |