Searched hist:"106 b09c1" (Results 1 – 3 of 3) sorted by relevance
/openbmc/docs/security/ |
H A D | obmc-security-response-team.md | 106b09c1 Wed Jul 27 17:02:39 CDT 2022 Joseph Reynolds <joseph-reynolds@charter.net> Use github security advisories
This updates the OpenBMC security vulnerability reporting process to use GitHub advisories. Each repository owner/maintainer is responsible for their security problems, and the security response team advises and creates CVEs.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: Ic9e169b4c94b625c9af838ef0c03c78fa0300031
|
H A D | how-to-report-a-security-vulnerability.md | 106b09c1 Wed Jul 27 17:02:39 CDT 2022 Joseph Reynolds <joseph-reynolds@charter.net> Use github security advisories
This updates the OpenBMC security vulnerability reporting process to use GitHub advisories. Each repository owner/maintainer is responsible for their security problems, and the security response team advises and creates CVEs.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: Ic9e169b4c94b625c9af838ef0c03c78fa0300031
|
H A D | obmc-security-response-team-guidelines.md | 106b09c1 Wed Jul 27 17:02:39 CDT 2022 Joseph Reynolds <joseph-reynolds@charter.net> Use github security advisories
This updates the OpenBMC security vulnerability reporting process to use GitHub advisories. Each repository owner/maintainer is responsible for their security problems, and the security response team advises and creates CVEs.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: Ic9e169b4c94b625c9af838ef0c03c78fa0300031
|