From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A0F34C7618F for ; Thu, 18 Jul 2019 22:00:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6BA08208C0 for ; Thu, 18 Jul 2019 22:00:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="fvjXH2nb" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391295AbfGRWA6 (ORCPT ); Thu, 18 Jul 2019 18:00:58 -0400 Received: from mail-pf1-f193.google.com ([209.85.210.193]:32925 "EHLO mail-pf1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727780AbfGRWA5 (ORCPT ); Thu, 18 Jul 2019 18:00:57 -0400 Received: by mail-pf1-f193.google.com with SMTP id g2so13231274pfq.0 for ; Thu, 18 Jul 2019 15:00:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=8xR8jl+9vgMnbRgGnFx+VtGRpj/KzIWKtjg0q2reL/k=; b=fvjXH2nbjQoatTbzrPNj3OZ46b6cJ+8n6SnDBNxFLsZs+Ehs5Nb2/vKueM3hgJyOJK driQhgj5ndG2WvD3hJDb/eqBOZJjflB58QRW/rS+Ul8xcwNxLk/NouJA0iGnkoyDGFRk eBOQekrr6gV7U/V3SAiqCidSranhnIz6b24Kc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=8xR8jl+9vgMnbRgGnFx+VtGRpj/KzIWKtjg0q2reL/k=; b=ggbltCyuSYEtDTBLf0jwqb9FX+UE8SdE5GlBfOnXsZcifYF1AzdNp0d2V2RrcHuSgr DSK9EYYYLDbJ+vlJ+EdG+w+pqab9x6VYo+q1MvZCE+JQ0ez6uRrUkts4YYeWAGEyO/oV jXteWe+ZXHPyRIgx+KxnH4f58xGTfQc1k5X9dqGkgAf6p5csLowJTP9uZhX2KeBfxHDH vYAEQ9WYprr+v2sUP9/DPfvyjj/NKXCQCJQ1pKitB7XCWj3dHJ6McJ1OJveitbzi5tjW kTC8I1dQD1kIVYb+tQ6IUKcItbjo3+wy3NPXzmFVBpfl5JEw5k3R7slnZRf7JlJ3isBO JSBQ== X-Gm-Message-State: APjAAAXX+WtnuCJckxrxqkDu6N53HGSUfkfX1S6vwYuwsCegVJNmMVv7 jCvEu7PVYvNgq+cqnD8xbUMKQA== X-Google-Smtp-Source: APXvYqwHrAAKS7n0aYl9H4nAYcLxIe5S0CqR2dUHEXjXNNZYBdVXXjPs1QuIMv19nVjZhcPF43F+OQ== X-Received: by 2002:a63:3203:: with SMTP id y3mr50691914pgy.191.1563487256758; Thu, 18 Jul 2019 15:00:56 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id 124sm30444223pfw.142.2019.07.18.15.00.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 18 Jul 2019 15:00:56 -0700 (PDT) Date: Thu, 18 Jul 2019 15:00:55 -0700 From: Kees Cook To: Sasha Levin Cc: corbet@lwn.net, solar@openwall.com, will@kernel.org, peterz@infradead.org, gregkh@linuxfoundation.org, tyhicks@canonical.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] Documentation/security-bugs: provide more information about linux-distros Message-ID: <201907181457.D61AC061C@keescook> References: <20190717231103.13949-1-sashal@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190717231103.13949-1-sashal@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 17, 2019 at 07:11:03PM -0400, Sasha Levin wrote: > 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 > security@kernel.org's policy. > > Suggested-by: Solar Designer > Signed-off-by: Sasha Levin Sorry, but NACK, see below... > --- > > 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? > - 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. > - 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 > > Documentation/admin-guide/security-bugs.rst | 19 +++++++++---------- > 1 file changed, 9 insertions(+), 10 deletions(-) > > diff --git a/Documentation/admin-guide/security-bugs.rst b/Documentation/admin-guide/security-bugs.rst > index dcd6c93c7aac..380d44fd618d 100644 > --- a/Documentation/admin-guide/security-bugs.rst > +++ b/Documentation/admin-guide/security-bugs.rst > @@ -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 > - 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: > - > +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: > +. 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 > -------------- > -- > 2.20.1 > -- Kees Cook