From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-6.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id BD0DD7D90D for ; Thu, 11 Jul 2019 16:36:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728517AbfGKQgp (ORCPT ); Thu, 11 Jul 2019 12:36:45 -0400 Received: from mail.kernel.org ([198.145.29.99]:39568 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726213AbfGKQgp (ORCPT ); Thu, 11 Jul 2019 12:36:45 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1EBA620863; Thu, 11 Jul 2019 16:36:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562863004; bh=SRPiMyIccRI4B0O/NdGPz8Oetbs1P8gxCt0qlY6hKxE=; h=From:To:Cc:Subject:Date:From; b=eg+GSZ7e1xYuoLRBS2980GM1FfYNwoASK5NjfQgLbXXQwJ0/Rxxb64NXfbTcHossB T7EGMuNIHLkt+CY7CDYdN4BJKtt+wyc7bextGuy6SoUNH/XIfVZASoETKO/A1ezbS0 5jF8mdLEYPmztGqJqzrR0ZkpFYvxuM3sVahTu33w= From: Sasha Levin To: corbet@lwn.net, solar@openwall.com Cc: will@kernel.org, keescook@chromium.org, peterz@infradead.org, gregkh@linuxfoundation.org, tyhicks@canonical.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Sasha Levin Subject: [PATCH] Documentation/security-bugs: provide more information about linux-distros Date: Thu, 11 Jul 2019 12:36:37 -0400 Message-Id: <20190711163637.30327-1-sashal@kernel.org> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org 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 Signed-off-by: Sasha Levin --- Documentation/admin-guide/security-bugs.rst | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/Documentation/admin-guide/security-bugs.rst b/Documentation/admin-guide/security-bugs.rst index dcd6c93c7aac..c62faced9256 100644 --- a/Documentation/admin-guide/security-bugs.rst +++ b/Documentation/admin-guide/security-bugs.rst @@ -61,14 +61,19 @@ 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: + mailing list so that distribution vendors are +well prepared to issue a fixed kernel upon public disclosure of the upstream +fix. As a reporter, you must read and accept the list's policy as outlined in +the linux-distros wiki: +. +When you report a bug, you must also provide a tentative disclosure date and +time in your very first message to the list. Distros will need some time to +test the proposed patch so please allow 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: CVE assignment -- 2.20.1