From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Conor Dooley <conor@kernel.org>, 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: Re: [PATCH v1] Documentation: process: Document suitability of Proton Mail for kernel development
Date: Wed, 28 Dec 2022 19:33:53 +0700 [thread overview]
Message-ID: <32a201f7-fb1a-0651-6b82-b2593e56e759@gmail.com> (raw)
In-Reply-To: <20221228000330.3971104-1-conor@kernel.org>
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.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-12-28 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 0:03 [PATCH v1] Documentation: process: Document suitability of Proton Mail for kernel development Conor Dooley
2022-12-28 12:33 ` Bagas Sanjaya [this message]
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=32a201f7-fb1a-0651-6b82-b2593e56e759@gmail.com \
--to=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox