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=-5.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, 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 0323E7D2F0 for ; Fri, 2 Aug 2019 06:57:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389183AbfHBG5d (ORCPT ); Fri, 2 Aug 2019 02:57:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:34520 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389177AbfHBG5d (ORCPT ); Fri, 2 Aug 2019 02:57:33 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C82FC2086A; Fri, 2 Aug 2019 06:57:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564729052; bh=ffM+LICWllxWJE/vQvAaeiAc+X9tSUkA68IQmo2LQ9g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fAItImq9S90rX9l+DgsGbTRR+l8aOgIVns7ZwcBkAamUtiBQjgh6/Za1osWY0q23I aYBBMz53C9J2HvskmWRFcNgWGgE+V9kj6KVbnQ2GwvB2sVM+W884Bm8B/yqdlp8uCA TcTJFAPXluoI+zaj5nOyt7BgxDxEdzs/MgG2LCA8= Date: Fri, 2 Aug 2019 08:57:29 +0200 From: Greg Kroah-Hartman To: Willy Tarreau Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, Jonathan Corbet , security@kernel.org, linux-doc@vger.kernel.org, Jiri Kosina , Mauro Carvalho Chehab Subject: Re: [PATCH] Documentation/admin-guide: Embargoed hardware security issues Message-ID: <20190802065729.GA24024@kroah.com> References: <20190725130113.GA12932@kroah.com> <20190802044908.GA12834@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190802044908.GA12834@1wt.eu> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Fri, Aug 02, 2019 at 06:49:08AM +0200, Willy Tarreau wrote: > Hi Greg, Thomas, > > On Thu, Jul 25, 2019 at 03:01:13PM +0200, Greg Kroah-Hartman wrote: > > +The list is encrypted and email to the list can be sent by either PGP or > > +S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME > > +certificate. The list's PGP key and S/MIME certificate are available from > > +https://www.kernel.org/.... > > Just thinking, wouldn't it be useful to strongly encourage that the > document should be in plain text format ? Otherwise the door remains open > for sending you a self-extractable EXE file which contains an encrypted > Word doc, which is not the most useful to handle especially to copy-paste > mitigation code nor to comment on. Even some occasional PDFs we've seen > on the sec@k.o list were sometimes quite detailed but less convenient > than the vast majority of plain text ones, particularly when it comes > to quoting some parts. What document are you referring to here? This just describes how the encrypted mailing list is going to work, not anything else. But yes, we have had some "encrypted pdfs" be sent to us recently that no one can decrypt unless they run Windows or do some really crazy hacks with the gstreamer pipeline. But that's separate from this specific mailing list, we can always just tell people to not do foolish things if that happens again (like we did in this case.) thanks, greg k-h