Skip to contentSkip to conversation

Add SECURITY.md

PATCH Superseded Marta Rybczynska 2 participants 4 messages Oct 17, 2023 – Oct 19, 2023

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Add SECURITY.md

Add a SECURITY.md filr with hints for security researchers and other parties who might report potential security vulnerabilities.

---
 SECURITY.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 SECURITY.md
SECURITY.md new file +17 -0
new file mode 100644
index 0000000000..900da76e59
@@ -0,0 +1,17 @@
+How to Report a Vulnerability?
+==============================
+
+Please send a message to security AT yoctoproject DOT org, including as many details
+as possible: the layer or software module affected, the recipe and its version,
+and any example code, if available.
+
+Branches maintained with security fixes
+---------------------------------------
+
+See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]
+for detailed info regarding the policies and maintenance of Stable branch.
+
+The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all
+releases of the Yocto Project. Versions in grey are no longer actively maintained with
+security patches, but well-tested patches may still be accepted for them for
+significant issues.
Signature · 1 line
2.39.2
#1 lore raw
Quoted 15 lines · Marta Rybczynska

Add a SECURITY.md filr with hints for security researchers and other parties who might report potential security vulnerabilities.

---
 SECURITY.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 SECURITY.md
SECURITY.md new file +0 -0
new file mode 100644
index 0000000000..900da76e59

SECURITY.md line 6

Quoted 6 lines
SECURITY.md new file +6 -0
@@ -0,0 +1,17 @@
+How to Report a Vulnerability?
+==============================
+
+Please send a message to security AT yoctoproject DOT org, including as many details
+as possible: the layer or software module affected, the recipe and its version,
+and any example code, if available.

Rather than send everyone to the security address, can we suggest bugzilla as the first port of call for anything public knowledge and less urgent and to only to use the security address for non-public or urgent issues?

We do have the ability to mark bugs as security and private and then triage unlocks them too.

Cheers,

Richard

#2 lore raw
Quoted 29 lines · Richard Purdie
Quoted 15 lines · Marta Rybczynska

Add a SECURITY.md filr with hints for security researchers and other parties who might report potential security vulnerabilities.

---
 SECURITY.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 SECURITY.md
SECURITY.md new file +0 -0
new file mode 100644
index 0000000000..900da76e59

SECURITY.md line 6

Quoted 6 lines
SECURITY.md new file +6 -0
@@ -0,0 +1,17 @@
+How to Report a Vulnerability?
+==============================
+
+Please send a message to security AT yoctoproject DOT org, including as many details
+as possible: the layer or software module affected, the recipe and its version,
+and any example code, if available.

Rather than send everyone to the security address, can we suggest bugzilla as the first port of call for anything public knowledge and less urgent and to only to use the security address for non-public or urgent issues?

Quoted 3 lines

We do have the ability to mark bugs as security and private and then triage unlocks them too.

Absolutely. I will be sending a v2 to OE-core only. When we agree on this one, I will send it also to other layers. As they might come in different combinations,
a SECURITY.md for each layer (like README) gives us best visibility.

Regards,
Marta

#3 lore raw
Quoted 31 lines · Marta Rybczynska
Quoted 29 lines · Richard Purdie
Quoted 15 lines · Marta Rybczynska

Add a SECURITY.md filr with hints for security researchers and other parties who might report potential security vulnerabilities.

---
 SECURITY.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 SECURITY.md
SECURITY.md new file +0 -0
new file mode 100644
index 0000000000..900da76e59

SECURITY.md line 6

Quoted 6 lines
SECURITY.md new file +6 -0
@@ -0,0 +1,17 @@
+How to Report a Vulnerability?
+==============================
+
+Please send a message to security AT yoctoproject DOT org, including as many details
+as possible: the layer or software module affected, the recipe and its version,
+and any example code, if available.

Rather than send everyone to the security address, can we suggest bugzilla as the first port of call for anything public knowledge and less urgent and to only to use the security address for non-public or urgent issues?

Quoted 8 lines
Quoted 3 lines

We do have the ability to mark bugs as security and private and then triage unlocks them too.

Absolutely. I will be sending a v2 to OE-core only. When we agree on this one, I will send it also to other layers. As they might come in different combinations,
a SECURITY.md for each layer (like README) gives us best visibility.

I'm happy with the OE-Core v2 so plan to merge that to the nanbield and master branches even if we've built rc1. I'm assuming Steve will add to the LTS branches too?

Cheers,

Richard