[v1] Documentation: process: Document suitability of Proton Mail for kernel development
Message ID | 20221228000330.3971104-1-conor@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp1649158wrt; Tue, 27 Dec 2022 16:36:30 -0800 (PST) X-Google-Smtp-Source: AMrXdXtvYF1k1KkNSM0d42FJk8f63d6bEE+E/ZJpVr+LlEqCC5bSZbcHxEmaxs4cVUdBJozlrk9i X-Received: by 2002:a17:903:493:b0:192:50fe:5051 with SMTP id jj19-20020a170903049300b0019250fe5051mr25529570plb.26.1672187790392; Tue, 27 Dec 2022 16:36:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672187790; cv=none; d=google.com; s=arc-20160816; b=Z/Fn2l4xjcUaT56dbY2JxNvAjUnvEJImCU7kAflugFhExwLqiy9GKj48Ag0bSg+S2p MxIbvNRBqrabxgI5DsDccniw8CRQQ3m3WstdFf52Jgy/6n8h8StAFM7l8gkPvkb+rNsp 547WRFA8Znt3kyztiTZ98zO34z7eX+mzgcLEj6yNVrAqLx0vgxlNR21FO7u3PWZe/DHu qWkj7i7pBot+qX/AiNzvEkbT91PjPex2dh1HV/6kWLdxQXg1VFC2+aHWhwd71RsHR/rz SU0vxVa0CBipjJzvv9ZV1g43jSnN7vNIyOllk2HjMH+JOj12p36KNbbrHHJIb6tq9Yid fhew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=mZp7Y9C54DXSdWrMKNY247u0Lgh2h8T/zeembrIN4MY=; b=pQ9Tf6ENJXdnV3xmcXo3BS0gY8Op/vKD08YusTV2gM4A2MhqZM2P+s38CTD65SaaGk sXPlT7n/hhdgadmXzV8XU1LPQ9oQR7OEJkfvz12yMkBgom2FIT+m0xC58gHcUYBb+zFS 1PAo76GeSeWMWeROp34vRhnDZuymKVINYfI798f4d9tfk44ez+EdYTsFjEqcB/U+mv0N pyKXv/eKFq0v9EjiQH9JYO2fpmDPecjrUKKZx6o+bFlr2GWhYwsCajwYyrhNyVFk3iYB SoZBmrZ6pzWsQLxAvU5UlK/r3WjDpV+I0o5yLye2pI0/IZgAUspA8/XHPwfbuje95QuV S3Vw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=u7FYZKV+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d4-20020a170902cec400b00178b95aa01fsi16858274plg.614.2022.12.27.16.36.18; Tue, 27 Dec 2022 16:36:30 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=u7FYZKV+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229840AbiL1ADz (ORCPT <rfc822;eddaouddi.ayoub@gmail.com> + 99 others); Tue, 27 Dec 2022 19:03:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229502AbiL1ADy (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 27 Dec 2022 19:03:54 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4745E5593; Tue, 27 Dec 2022 16:03:53 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id E70FFB81211; Wed, 28 Dec 2022 00:03:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 36E5CC433EF; Wed, 28 Dec 2022 00:03:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1672185830; bh=MQbih2jbIEW/jJUbyRpVyIdJTyGdXQtXDMaw+tQ/Hf8=; h=From:To:Cc:Subject:Date:From; b=u7FYZKV+YsqKvFBDe8HzubR9FBcyvRTIhcenog870EfS72mvXJaskwFZT2hc0O3uC XHCfQO+tfL0qD4eWuR7UU8MYTFcYZ9DBBNArYXHOp9zjPU8njkyX8Z6FrZLR+Yi4gX 32d9ivNn32o0XXIB9rsQ+C0U1l9JqKD3VawZHJ0S1KDrD+e3g8+CAOFloJwTjQxahi jq3wIyLZ/C5V2+ygmk68wQpLZcZTv7OydjtKh5HPkCiI5/hsxhxk4yShbVGqg1Rpsf luCE/oitl6lF+NHanNu64Hwzt8srg3/dgA0S2f9YL0TA0hyoOjnizHohQno97KZIj9 rHZW9QQnGLJcQ== From: Conor Dooley <conor@kernel.org> To: corbet@lwn.net Cc: Conor Dooley <conor.dooley@microchip.com>, broonie@kernel.org, konstantin@linuxfoundation.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v1] Documentation: process: Document suitability of Proton Mail for kernel development Date: Wed, 28 Dec 2022 00:03:31 +0000 Message-Id: <20221228000330.3971104-1-conor@kernel.org> X-Mailer: git-send-email 2.38.1 MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=1644; i=conor.dooley@microchip.com; h=from:subject; bh=eniW2kbAbZifJ5f8/X496o8vI0+UsoIVdT7XOxxhr/g=; b=owGbwMvMwCFWscWwfUFT0iXG02pJDMmr2y/orbfZ7aOV6lagv6d0E8O2VzNUmQoufMoyLpsk9PWf /6TFHaUsDGIcDLJiiiyJt/tapNb/cdnh3PMWZg4rE8gQBi5OAZjIifWMDC9yJxd8e91z6Vq8zMMDSr fP35azlPzioTDh0R0jcUWh8C+MDP3ervGnfHqKL0z9JMP7NHFCwLaAgFXJQic7ZHt2X3jAzwsA X-Developer-Key: i=conor.dooley@microchip.com; a=openpgp; fpr=F9ECA03CF54F12CD01F1655722E2C55B37CF380C Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1753415984858553047?= X-GMAIL-MSGID: =?utf-8?q?1753415984858553047?= |
Series |
[v1] Documentation: process: Document suitability of Proton Mail for kernel development
|
|
Commit Message
Conor Dooley
Dec. 28, 2022, 12:03 a.m. UTC
From: Conor Dooley <conor.dooley@microchip.com> Proton Mail automatically picks up PGP keys for those with kernel.org accounts (and other domains!) which provide WKD for their users & uses them to encrypt emails, including patches. Document the behaviour & Proton Mail's unsuitability for kernel development. Signed-off-by: Conor Dooley <conor.dooley@microchip.com> --- Documentation/process/email-clients.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
Comments
On 12/28/22 07:03, Conor Dooley wrote: > + > +Proton Mail > +*********** > + > +Proton Mail has a "feature" where it looks up keys using Web Key Directory > +(WKD) and encrypts mail to any email recipients for which it finds a key. > +Kernel.org publishes the WKD for all developers who have kernel.org accounts. > +As a result, emails sent using Proton Mail to kernel.org addresses will be > +encrypted. > +Unfortunately, Proton Mail does not provide a mechanism to disable the > +automatic encryption, viewing it as a privacy feature. > +This affects mail sent from their web GUI, from other mail clients using their > +mail "bridge", as well as patches sent using ``git send-email``. > +Unless a way to disable this "feature" is introduced, Proton Mail is unsuited > +to kernel development. All mails sent via Proton Mail SMTP relay? Also, why is sending encrypted emails to public mailing lists (like LKML) not a good idea? Thanks.
+CC Joe & Alexander, who were the ones that had the problem. On Wed, Dec 28, 2022 at 07:33:53PM +0700, Bagas Sanjaya wrote: > On 12/28/22 07:03, Conor Dooley wrote: > > + > > +Proton Mail > > +*********** > > + > > +Proton Mail has a "feature" where it looks up keys using Web Key Directory > > +(WKD) and encrypts mail to any email recipients for which it finds a key. > > +Kernel.org publishes the WKD for all developers who have kernel.org accounts. > > +As a result, emails sent using Proton Mail to kernel.org addresses will be > > +encrypted. > > +Unfortunately, Proton Mail does not provide a mechanism to disable the > > +automatic encryption, viewing it as a privacy feature. > > +This affects mail sent from their web GUI, from other mail clients using their > > +mail "bridge", as well as patches sent using ``git send-email``. > > +Unless a way to disable this "feature" is introduced, Proton Mail is unsuited > > +to kernel development. > > All mails sent via Proton Mail SMTP relay? I'm not quite sure what the purpose of your question is, sorry. When I say "bridge", I mean their program by the same name: https://proton.me/mail/bridge When I was using proton, I do not recall being able to send mail using proton without the bridge, their web GUI or their app. Perhaps Joe or Alexander are aware of anything that's changed in the last year. > Also, why is sending encrypted emails > to public mailing lists (like LKML) not a good idea? Is that a real or rhetorical question? Note that the public mailing list *does not* receive the encrypted copies of the emails. Thanks, Conor.
On Wed, Dec 28, 2022 at 12:03:31AM +0000, Conor Dooley wrote: > +Proton Mail has a "feature" where it looks up keys using Web Key Directory > +(WKD) and encrypts mail to any email recipients for which it finds a key. > +Kernel.org publishes the WKD for all developers who have kernel.org accounts. > +As a result, emails sent using Proton Mail to kernel.org addresses will be > +encrypted. > +Unfortunately, Proton Mail does not provide a mechanism to disable the > +automatic encryption, viewing it as a privacy feature. I'd perhaps add a note here that the reason the encryption is a problem is that developers may not have their mail client set up for easy and fluid operation with encrypted mail, making the process of reading the mail needlessly difficult, or it may cause some mail clients to encrypt replies to everyone including the list which obviously won't work well. But that's not essential, either way Reviewed-by: Mark Brown <broonie@kernel.org>
On Wed, Dec 28, 2022 at 12:03:31AM +0000, Conor Dooley wrote: > +This affects mail sent from their web GUI, from other mail clients using their > +mail "bridge", as well as patches sent using ``git send-email``. I suggest a minor tweak to wording here: The automatic encryption feature is also enabled for mail sent via the Proton Mail Bridge, so this affects all outgoing messages, including patches sent with ``git send-email``. > +Unless a way to disable this "feature" is introduced, Proton Mail is unsuited > +to kernel development. Reviewed-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org> Thanks! -K
diff --git a/Documentation/process/email-clients.rst b/Documentation/process/email-clients.rst index fc2c46f3f82d..c448f2814b84 100644 --- a/Documentation/process/email-clients.rst +++ b/Documentation/process/email-clients.rst @@ -350,3 +350,18 @@ although tab2space problem can be solved with external editor. Another problem is that Gmail will base64-encode any message that has a non-ASCII character. That includes things like European names. + +Proton Mail +*********** + +Proton Mail has a "feature" where it looks up keys using Web Key Directory +(WKD) and encrypts mail to any email recipients for which it finds a key. +Kernel.org publishes the WKD for all developers who have kernel.org accounts. +As a result, emails sent using Proton Mail to kernel.org addresses will be +encrypted. +Unfortunately, Proton Mail does not provide a mechanism to disable the +automatic encryption, viewing it as a privacy feature. +This affects mail sent from their web GUI, from other mail clients using their +mail "bridge", as well as patches sent using ``git send-email``. +Unless a way to disable this "feature" is introduced, Proton Mail is unsuited +to kernel development.