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 [thread overview]
Message-ID: <20221228000330.3971104-1-conor@kernel.org> (raw)
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(+)
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.
--
2.38.1
next reply other threads:[~2022-12-28 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 0:03 Conor Dooley [this message]
2022-12-28 12:33 ` [PATCH v1] Documentation: process: Document suitability of Proton Mail for kernel development Bagas Sanjaya
2022-12-28 13:06 ` Conor Dooley
2022-12-29 13:13 ` Mark Brown
2022-12-30 19:43 ` Konstantin Ryabitsev
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=20221228000330.3971104-1-conor@kernel.org \
--to=conor@kernel.org \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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.