Skip to contentSkip to conversation

Documentation/security-bugs: provide more information about linux-distros

PATCH In review Sasha Levin 4 participants 9 messages Jul 17, 2019 – Jul 23, 2019 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 Documentation/security-bugs: provide more information about linux-distros

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.
- Remove explicit linux-distros email.
- Remove various explanations of linux-distros policies.

 Documentation/admin-guide/security-bugs.rst | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)
Documentation/admin-guide/security-bugs.rst +9 -10
index dcd6c93c7aac..380d44fd618d 100644
@@ -60,16 +60,15 @@ Coordination
 ------------
 
 Fixes for sensitive bugs, such as those that might lead to privilege
-escalations, may need to be coordinated with the private
-<[email protected]> mailing list so that distribution vendors
-are well prepared to issue a fixed kernel upon public disclosure of the
-upstream fix. Distros will need some time to test the proposed patch and
-will generally request at least a few days of embargo, and vendor update
-publication prefers to happen Tuesday through Thursday. When appropriate,
-the security team can assist with this coordination, or the reporter can
-include linux-distros from the start. In this case, remember to prefix
-the email Subject line with "[vs]" as described in the linux-distros wiki:
-<http://oss-security.openwall.org/wiki/mailing-lists/distros#how-to-use-the-lists>
+escalations, may need to be coordinated with the private linux-distros mailing
+list so that distribution vendors are well prepared to issue a fixed kernel
+upon public disclosure of the upstream fix. Please read and follow the policies
+of linux-distros as specified in the linux-distros wiki page before reporting:
+<https://oss-security.openwall.org/wiki/mailing-lists/distros>. When
+appropriate, the security team can assist with this coordination, or the
+reporter can include linux-distros from the start. In this case, remember to
+prefix the email Subject line with "[vs]" as described in the linux-distros
+wiki.
 
 CVE assignment
 --------------
Signature · 1 line
2.20.1
#1 lore raw
Quoted 31 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.
- Remove explicit linux-distros email.
- Remove various explanations of linux-distros policies.

 Documentation/admin-guide/security-bugs.rst | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)
Documentation/admin-guide/security-bugs.rst +0 -4
index dcd6c93c7aac..380d44fd618d 100644
@@ -60,16 +60,15 @@ Coordination
 ------------
 
 Fixes for sensitive bugs, such as those that might lead to privilege
-escalations, may need to be coordinated with the private
-<[email protected]> mailing list so that distribution vendors
-are well prepared to issue a fixed kernel upon public disclosure of the
-upstream fix. Distros will need some time to test the proposed patch and

Documentation/admin-guide/security-bugs.rst Coordination · line 66

Quoted 10 lines
Documentation/admin-guide/security-bugs.rst +4 -6
-will generally request at least a few days of embargo, and vendor update
-publication prefers to happen Tuesday through Thursday. When appropriate,
-the security team can assist with this coordination, or the reporter can
-include linux-distros from the start. In this case, remember to prefix
-the email Subject line with "[vs]" as described in the linux-distros wiki:
-<http://oss-security.openwall.org/wiki/mailing-lists/distros#how-to-use-the-lists>
+escalations, may need to be coordinated with the private linux-distros mailing
+list so that distribution vendors are well prepared to issue a fixed kernel
+upon public disclosure of the upstream fix. Please read and follow the policies
+of linux-distros as specified in the linux-distros wiki page before reporting:

can we add a "there" at the end of this sentence, so it can't be misread as implying that you must follow the linux-distros policies before reporting to [email protected] ?

Will

#2 lore raw
Quoted 38 lines · Will Deacon
Quoted 37 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.
- Remove explicit linux-distros email.
- Remove various explanations of linux-distros policies.

 Documentation/admin-guide/security-bugs.rst | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)
Documentation/admin-guide/security-bugs.rst +0 -10
index dcd6c93c7aac..380d44fd618d 100644
@@ -60,16 +60,15 @@ Coordination
 ------------
 
 Fixes for sensitive bugs, such as those that might lead to privilege
-escalations, may need to be coordinated with the private
-<[email protected]> mailing list so that distribution vendors
-are well prepared to issue a fixed kernel upon public disclosure of the
-upstream fix. Distros will need some time to test the proposed patch and
-will generally request at least a few days of embargo, and vendor update
-publication prefers to happen Tuesday through Thursday. When appropriate,
-the security team can assist with this coordination, or the reporter can
-include linux-distros from the start. In this case, remember to prefix
-the email Subject line with "[vs]" as described in the linux-distros wiki:
-<http://oss-security.openwall.org/wiki/mailing-lists/distros#how-to-use-the-lists>
Quoted 8 lines

Documentation/admin-guide/security-bugs.rst Coordination · line 66

Quoted 4 lines
Documentation/admin-guide/security-bugs.rst +4 -0
+escalations, may need to be coordinated with the private linux-distros mailing
+list so that distribution vendors are well prepared to issue a fixed kernel
+upon public disclosure of the upstream fix. Please read and follow the policies
+of linux-distros as specified in the linux-distros wiki page before reporting:

can we add a "there" at the end of this sentence, so it can't be misread as implying that you must follow the linux-distros policies before reporting to [email protected] ?

Sasha's patch above and the addition suggested by Will look good to me.

Thanks!

Alexander

#3 lore raw
In reply to Sasha Levin
Quoted 9 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

Sorry, but NACK, see below...

Quoted 4 lines

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.

I think this is already happening in the text. What specifically do you want described differently?

Quoted 1 line

- Remove explicit linux-distros email.

I don't like this because we had past trouble with notifications going to the distros@ list and leaking Linux-only flaws to the BSDs. As there isn't a separate linux-distros wiki, the clarification of WHICH list is needed.

Quoted 1 line

- Remove various explanations of linux-distros policies.

I don't think there's value in removing the Tue-Thu comment, nor providing context for why distros need time. This has been a regular thing we've had to explain to researchers that aren't familiar with update procedures and publication timing.

-Kees

Quoted 37 lines
 Documentation/admin-guide/security-bugs.rst | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)
Documentation/admin-guide/security-bugs.rst +9 -10
index dcd6c93c7aac..380d44fd618d 100644
@@ -60,16 +60,15 @@ Coordination
 ------------
 
 Fixes for sensitive bugs, such as those that might lead to privilege
-escalations, may need to be coordinated with the private
-<[email protected]> mailing list so that distribution vendors
-are well prepared to issue a fixed kernel upon public disclosure of the
-upstream fix. Distros will need some time to test the proposed patch and
-will generally request at least a few days of embargo, and vendor update
-publication prefers to happen Tuesday through Thursday. When appropriate,
-the security team can assist with this coordination, or the reporter can
-include linux-distros from the start. In this case, remember to prefix
-the email Subject line with "[vs]" as described in the linux-distros wiki:
-<http://oss-security.openwall.org/wiki/mailing-lists/distros#how-to-use-the-lists>
+escalations, may need to be coordinated with the private linux-distros mailing
+list so that distribution vendors are well prepared to issue a fixed kernel
+upon public disclosure of the upstream fix. Please read and follow the policies
+of linux-distros as specified in the linux-distros wiki page before reporting:
+<https://oss-security.openwall.org/wiki/mailing-lists/distros>. When
+appropriate, the security team can assist with this coordination, or the
+reporter can include linux-distros from the start. In this case, remember to
+prefix the email Subject line with "[vs]" as described in the linux-distros
+wiki.
 
 CVE assignment
 --------------
Signature · 1 line
2.20.1
Signature · 1 line
Kees Cook
#4 lore raw
Quoted 13 lines · Kees Cook
Quoted 9 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

Sorry, but NACK, see below...

Quoted 7 lines
Quoted 4 lines

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.

I think this is already happening in the text. What specifically do you want described differently?

The main issue was that there isn't anything pointing to the linux-distros policies. The current text outlines a few of them ("add [vs]", and "there should be an embargo period"), but it effectively just gives out the linux-distros mailing address and tells the reporter to contact it.

Quoted 6 lines
Quoted 1 line

- Remove explicit linux-distros email.

I don't like this because we had past trouble with notifications going to the distros@ list and leaking Linux-only flaws to the BSDs. As there isn't a separate linux-distros wiki, the clarification of WHICH list is needed.

Why would removing the explicit linux-distros email encourage people to send reports to it?

I also don't understand what you mean by "there isn't a separate linux-distros wiki"? There is one, and I want to point the reporter there.

Quoted 6 lines
Quoted 1 line

- Remove various explanations of linux-distros policies.

I don't think there's value in removing the Tue-Thu comment, nor providing context for why distros need time. This has been a regular thing we've had to explain to researchers that aren't familiar with update procedures and publication timing.

To be fair, the Tue-Thu comment is listed in the section describing how to do coordination with linux-distros, and linux-distros don't have a Tue-Thu policy. If it's a [email protected] policy then let's list it elsewhere.

If you feel that there is a consensus around Tue-Thu let's just add it to the linux-distros policy wiki, there's no point in listing random policies from that wiki.

--
Thanks,
Sasha

#5 lore raw
Quoted 19 lines · Sasha Levin
Quoted 18 lines · Kees Cook
Quoted 9 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

Sorry, but NACK, see below...

Quoted 4 lines

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.

Quoted 8 lines
Quoted 2 lines

I think this is already happening in the text. What specifically do you want described differently?

The main issue was that there isn't anything pointing to the linux-distros policies. The current text outlines a few of them ("add [vs]", and "there should be an embargo period"), but it effectively just gives out the linux-distros mailing address and tells the reporter to contact it.

The current text includes the wiki link, but yes, the anchor tag is not present at the wiki anymore. I would agree that's due for updating.

I think reinforcing information to avoid past mistakes is appropriate here. Reports have regularly missed the "[vs]" detail or suggested embargoes that ended on Fridays, etc.

Quoted 9 lines
Quoted 6 lines
Quoted 1 line

- Remove explicit linux-distros email.

I don't like this because we had past trouble with notifications going to the distros@ list and leaking Linux-only flaws to the BSDs. As there isn't a separate linux-distros wiki, the clarification of WHICH list is needed.

Why would removing the explicit linux-distros email encourage people to send reports to it?

What? No, I'm saying we should _keep_ linux-distros@... in our text so that people don't send to the wrong list.

Quoted 3 lines

I also don't understand what you mean by "there isn't a separate linux-distros wiki"? There is one, and I want to point the reporter there.

That URL is a combined page for two lists. The very fact that it's not obvious that there are two lists described there is exactly why I think we need to keep an explicit mention of which to use. There are two mailing lists described at the wiki URL:

[email protected]
[email protected]

Sending to the distros@ list risks exposing Linux-only flaws to non-Linux distros. This has caused leaks in the past, and we do not want people guessing at which list they should use.

Also note that nowhere on the openwall wiki is the email address actually spelled out; this is another reason to spell it out in our
documentation: no misunderstanding.

(And historically there WAS a specific linux-distros wiki:
https://oss-security.openwall.org/wiki/mailing-lists/linux-distros
but it redirects to the combined one now...)

Quoted 11 lines
Quoted 6 lines
Quoted 1 line

- Remove various explanations of linux-distros policies.

I don't think there's value in removing the Tue-Thu comment, nor providing context for why distros need time. This has been a regular thing we've had to explain to researchers that aren't familiar with update procedures and publication timing.

To be fair, the Tue-Thu comment is listed in the section describing how to do coordination with linux-distros, and linux-distros don't have a Tue-Thu policy. If it's a [email protected] policy then let's list it elsewhere.

It's a distro preference. Many researchers aren't thinking about the larger Linux ecosystem that has to consume fixes. It's not a _policy_, but it makes the researchers understand how to construct better embargoes.

Quoted 3 lines

If you feel that there is a consensus around Tue-Thu let's just add it to the linux-distros policy wiki, there's no point in listing random policies from that wiki.

I think it'd be a good idea to add that note also to the wiki, but I don't want it removed from our text because I have had to repeat that information regularly in the past.

Signature · 1 line
Kees Cook
#6 lore raw
Quoted 29 lines · Kees Cook
Quoted 19 lines · Sasha Levin
Quoted 18 lines · Kees Cook
Quoted 9 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

Sorry, but NACK, see below...

Quoted 4 lines

---

Changes in v2:
- Focus more on pointing to the linux-distros wiki and policies.

Quoted 8 lines
Quoted 2 lines

I think this is already happening in the text. What specifically do you want described differently?

The main issue was that there isn't anything pointing to the linux-distros policies. The current text outlines a few of them ("add [vs]", and "there should be an embargo period"), but it effectively just gives out the linux-distros mailing address and tells the reporter to contact it.

Quoted 6 lines

The current text includes the wiki link, but yes, the anchor tag is not present at the wiki anymore. I would agree that's due for updating.

I think reinforcing information to avoid past mistakes is appropriate here. Reports have regularly missed the "[vs]" detail or suggested embargoes that ended on Fridays, etc.

Right, but this is a sign that the reporter didn't read the wiki. Explaining things like this encourages reporters to skip reading the wiki and just send their report out.

Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
Quoted 1 line

- Remove explicit linux-distros email.

I don't like this because we had past trouble with notifications going to the distros@ list and leaking Linux-only flaws to the BSDs. As there isn't a separate linux-distros wiki, the clarification of WHICH list is needed.

Quoted 5 lines
Quoted 2 lines

Why would removing the explicit linux-distros email encourage people to send reports to it?

What? No, I'm saying we should _keep_ linux-distros@... in our text so that people don't send to the wrong list.

But doesn't this just encourage mails being sent to linux-distros@ without the policies being followed? That was Alexander's concern at least.

Quoted 31 lines
Quoted 3 lines

I also don't understand what you mean by "there isn't a separate linux-distros wiki"? There is one, and I want to point the reporter there.

That URL is a combined page for two lists. The very fact that it's not obvious that there are two lists described there is exactly why I think we need to keep an explicit mention of which to use. There are two mailing lists described at the wiki URL:

[email protected]
[email protected]

Sending to the distros@ list risks exposing Linux-only flaws to non-Linux distros. This has caused leaks in the past, and we do not want people guessing at which list they should use.

Also note that nowhere on the openwall wiki is the email address actually spelled out; this is another reason to spell it out in our
documentation: no misunderstanding.

(And historically there WAS a specific linux-distros wiki:
https://oss-security.openwall.org/wiki/mailing-lists/linux-distros
but it redirects to the combined one now...)

Quoted 7 lines
Quoted 6 lines
Quoted 1 line

- Remove various explanations of linux-distros policies.

I don't think there's value in removing the Tue-Thu comment, nor providing context for why distros need time. This has been a regular thing we've had to explain to researchers that aren't familiar with update procedures and publication timing.

Quoted 8 lines
Quoted 4 lines

To be fair, the Tue-Thu comment is listed in the section describing how to do coordination with linux-distros, and linux-distros don't have a Tue-Thu policy. If it's a [email protected] policy then let's list it elsewhere.

It's a distro preference. Many researchers aren't thinking about the larger Linux ecosystem that has to consume fixes. It's not a _policy_, but it makes the researchers understand how to construct better embargoes.

If it's an accepted preference then we should just document it in a few other places like the linux-distros@ wiki. My concern with this is that it's not, and it's actually one of the only things Alexander pointed out in this document as surprising.

--
Thanks,
Sasha

Quoted 10 lines
Quoted 3 lines

If you feel that there is a consensus around Tue-Thu let's just add it to the linux-distros policy wiki, there's no point in listing random policies from that wiki.

I think it'd be a good idea to add that note also to the wiki, but I don't want it removed from our text because I have had to repeat that information regularly in the past.

Signature · 1 line
Kees Cook
#7 lore raw
In reply to Kees Cook
Quoted 6 lines · Kees Cook
Quoted 5 lines · Sasha Levin
Quoted 4 lines · Kees Cook
Quoted 3 lines · Sasha Levin

Provide more information about how to interact with the linux-distros mailing list for disclosing security bugs.

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines

Reference the linux-distros list policy and clarify that the reporter must read and understand those policies as they differ from [email protected]'s policy.

Sorry, but NACK, see below...

I like Sasha's PATCH v2 better, but if Kees insists on NACK'ing it then I suggest that we apply Sasha's first revision of the patch instead. I think either revision is an improvement on the status quo.

Quoted 2 lines

I think reinforcing information to avoid past mistakes is appropriate here.

Maybe, but from my perspective common past issues with Linux kernel bugs reported to linux-distros were:

- The reporter having been directed to post from elsewhere (and I suspect this documentation file) without being aware of list policy.

- The reporter not mentioning (and sometimes not replying even when asked) whether they're also coordinating with [email protected] or whether they want someone on linux-distros to help coordinate with [email protected]. (Maybe this is something we want to write about here.)

- The Linux kernel bug having been introduced too recently to be of much interest to distros.

Quoted 2 lines

Reports have regularly missed the "[vs]" detail or suggested embargoes that ended on Fridays, etc.

This happens too. Regarding missing the "[vs]" detail, technically there are also a number of other conditions that also let the message through, but those are changing and are deliberately not advertised.

Quoted 2 lines

Sending to the distros@ list risks exposing Linux-only flaws to non-Linux distros.

Right.

Quoted 1 line

This has caused leaks in the past

Do you mean leaks to *BSD security teams or to the public? I'm not aware of past leaks to the public via the non-Linux distros present on the distros@ list. Are you?

Alexander

#8 lore raw
Quoted 2 lines · Solar Designer

- The reporter having been directed to post from elsewhere (and I suspect this documentation file) without being aware of list policy.

Perhaps specify "linux-distros@" without a domain, so it's more clear? Or re-split the Wiki into two pages to avoid confusion?

Quoted 4 lines

- The reporter not mentioning (and sometimes not replying even when asked) whether they're also coordinating with [email protected] or whether they want someone on linux-distros to help coordinate with [email protected]. (Maybe this is something we want to write about here.)

Yeah, that seems useful to include in both places.

Quoted 2 lines

- The Linux kernel bug having been introduced too recently to be of much interest to distros.

Right; that'd be good to add as well. I see a lot of panic on twitter, for example, about bugs that only ever existed in -rc releases.

Quoted 10 lines
Quoted 2 lines

Sending to the distros@ list risks exposing Linux-only flaws to non-Linux distros.

Right.

Quoted 1 line

This has caused leaks in the past

Do you mean leaks to *BSD security teams or to the public? I'm not aware of past leaks to the public via the non-Linux distros present on the distros@ list. Are you?

I don't know the origin of the leaks, but it only happened when distros@ was used instead of linux-distros@. I think this happened with DirtyCOW, specifically.

Signature · 1 line
Kees Cook