From: Solar Designer <solar@openwall.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
corbet@lwn.net, keescook@chromium.org, peterz@infradead.org,
tyhicks@canonical.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/security-bugs: provide more information about linux-distros
Date: Sun, 14 Jul 2019 20:05:55 +0200 [thread overview]
Message-ID: <20190714180555.GA8536@openwall.com> (raw)
In-Reply-To: <20190711203500.GB10104@sasha-vm>
On Thu, Jul 11, 2019 at 04:35:00PM -0400, Sasha Levin wrote:
> On Thu, Jul 11, 2019 at 06:09:21PM +0100, Will Deacon wrote:
> >On Thu, Jul 11, 2019 at 07:07:32PM +0200, Greg KH wrote:
> >>On Thu, Jul 11, 2019 at 12:36:37PM -0400, Sasha Levin wrote:
> >>> Provide more information about how to interact with the linux-distros
> >>> mailing list for disclosing security bugs.
> >>>
> >>> First, clarify that the reporter must read and accept the linux-distros
> >>> policies prior to sending a report.
> >>>
> >>> Second, clarify that the reported must provide a tentative public
> >>> disclosure date and time in his first contact with linux-distros.
> >>>
> >>> Suggested-by: Solar Designer <solar@openwall.com>
> >>> Signed-off-by: Sasha Levin <sashal@kernel.org>
> >>> ---
> >>> Documentation/admin-guide/security-bugs.rst | 21 +++++++++++++--------
> >>> 1 file changed, 13 insertions(+), 8 deletions(-)
Thanks. Sasha's proposed changes do address the two issues I pointed
out, so are an improvement. However:
> >>Do we really need to describe all of the information on how to use the
> >>distro list here? That's why we included the link, as it has all of
> >>this well spelled out and described. If anything, I would say we should
> >>say less in this document about what linux-distros do, as that is
> >>independent of the Linux security team.
> >
> >Agreed, and it also means that any changes linux-distros make to their
> >policy won't be reflecting in the numerous kernel trees out there, so a
> >link is much better imo.
I also agree with this.
> I agree that the 2nd part about embargo timelines is redundant, but I
> only addressed it because the document was already addressing embargos.
>
> I only now realized that the link we had there was just going to the
> main wiki page by mistake: the tag it was trying to point to was removed
> from the wiki page. We should probably update that too.
>
> With regards to the explicit instruction to agree with policies, I think
> we do need it there. Right now this section reads as "for embargoes work
> with linux-distros@vs.openwall.org, and btw they have a wiki which you
> may or may not need to read".
Yes, we should update the link, but maybe we should also drop the
posting e-mail address, which will ensure someone will have to check out
the link before they're able to post. This should allow us to drop the
summary of linux-distros policy and posting instructions, although maybe
they're beneficial to keep if we're confident we'd be maintaining this
summary to reflect possible changes on the linked page.
> We probably do need to stress here that linux-distros has different
> policies than security@kernel.org.
OK.
Alexander
prev parent reply other threads:[~2019-07-14 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 16:36 [PATCH] Documentation/security-bugs: provide more information about linux-distros Sasha Levin
2019-07-11 17:07 ` Greg KH
2019-07-11 17:09 ` Will Deacon
2019-07-11 20:35 ` Sasha Levin
2019-07-14 18:05 ` Solar Designer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190714180555.GA8536@openwall.com \
--to=solar@openwall.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=tyhicks@canonical.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.