OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/.github/SECURITY.md

23 lines
520 B
Markdown
Raw Normal View History

.github: Create Github security policy document This document will show up when a viewer selects the "Security" tab, and selects the "Security Policy". It has a brief introduction, and directs to the official documentation of the security policy. Signed-off-by: David Brown <david.brown@linaro.org>
2021-03-19 04:41:27 +08:00
# Security Policy
## Supported versions
The Zephyr project supports the following versions with security
updates:
- The most recent release, and the release prior to that.
- Active LTS releases.
SECURITY: Drop "patch level" from the supported version number list This commit drops the "patch level" from the supported version numbers listed in the security policy document because: 1. It currently does not convey any meaningful information (simply set to "0") and is really unnecessary because the support status is defined at the "minor" version level. 2. Updating the security policy document whenever there is a new "patch release" is arguably too noisy and does not add much value. Signed-off-by: Stephanos Ioannidis <stephanos.ioannidis@nordicsemi.no>
2023-02-20 19:13:58 +08:00
At this time, with the latest release of v3.3, the supported
.github: Create Github security policy document This document will show up when a viewer selects the "Security" tab, and selects the "Security Policy". It has a brief introduction, and directs to the official documentation of the security policy. Signed-off-by: David Brown <david.brown@linaro.org>
2021-03-19 04:41:27 +08:00
versions are:
SECURITY: Drop "patch level" from the supported version number list This commit drops the "patch level" from the supported version numbers listed in the security policy document because: 1. It currently does not convey any meaningful information (simply set to "0") and is really unnecessary because the support status is defined at the "minor" version level. 2. Updating the security policy document whenever there is a new "patch release" is arguably too noisy and does not add much value. Signed-off-by: Stephanos Ioannidis <stephanos.ioannidis@nordicsemi.no>
2023-02-20 19:13:58 +08:00
- v2.7: Current LTS
- v3.2: Prior release
- v3.3: Current release
.github: Create Github security policy document This document will show up when a viewer selects the "Security" tab, and selects the "Security Policy". It has a brief introduction, and directs to the official documentation of the security policy. Signed-off-by: David Brown <david.brown@linaro.org>
2021-03-19 04:41:27 +08:00
## Reporting process
Please see our [Security Vulnerability
Reporting](https://docs.zephyrproject.org/latest/security/reporting.html)
page for details on the process.