workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kanak Shilledar <kanakshilledar111@protonmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Conor Dooley <conor.dooley@microchip.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Mark Brown <broonie@kernel.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Documentation: process: Revert "Document suitability of Proton Mail for kernel development"
Date: Thu, 16 May 2024 16:00:10 +0000	[thread overview]
Message-ID: <4oW9pC38sSYZn96BW8abMfVpDDCmG4MDHwwmL73o5bP-WyHAutJ5j2GrSU17MCSWOKufViNl4q2zZUmwmN40evP5OK3QiMnUn2hsgWCYhl4=@protonmail.com> (raw)
In-Reply-To: <20240516-groin-slingshot-c3c3734d2f10@spud>

On Thursday, May 16th, 2024 at 9:05 PM, Conor Dooley <conor@kernel.org> wrote:

> From: Conor Dooley conor.dooley@microchip.com
> 
> 
> Revert commit 1d2ed9234c85 ("Documentation: process: Document
> suitability of Proton Mail for kernel development") as Proton disabled
> WKD for kernel.org addresses as a result of some interaction with
> Konstantin on social.kernel.org
> 
> Signed-off-by: Conor Dooley conor.dooley@microchip.com
> 
> ---
> 
> I tried to find the stuff on social.korg to provide a link
> but could not.
> 
> CC: kanakshilledar111@protonmail.com
> CC: Konstantin Ryabitsev konstantin@linuxfoundation.org
> 
> CC: Mark Brown broonie@kernel.org
> 
> CC: Jonathan Corbet corbet@lwn.net
> 
> CC: workflows@vger.kernel.org
> CC: linux-doc@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> ---
> Documentation/process/email-clients.rst | 20 --------------------
> 1 file changed, 20 deletions(-)
> 
> diff --git a/Documentation/process/email-clients.rst b/Documentation/process/email-clients.rst
> index 471e1f93fa09..fc2c46f3f82d 100644
> --- a/Documentation/process/email-clients.rst
> +++ b/Documentation/process/email-clients.rst
> @@ -350,23 +350,3 @@ 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 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.
> -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`.
> -Encrypted mail adds unnecessary friction, as other developers may not have mail
> -clients, or tooling, configured for use with encrypted mail and some mail
> -clients may encrypt responses to encrypted mail for all recipients, including
> -the mailing lists.
> -Unless a way to disable this "feature" is introduced, Proton Mail is unsuited
> -to kernel development.

Instead of completely removing the Proton Mail section, can we keep the mention about the Proton Mail bridge and the third-party hydroxide (https://github.com/emersion/hydroxide) bridge.

> --
> 2.43.0

Thanks and Regards,
Kanak Shilledar

  reply	other threads:[~2024-05-16 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 15:35 Conor Dooley
2024-05-16 16:00 ` Kanak Shilledar [this message]
2024-05-16 16:04   ` Conor Dooley
2024-05-17  9:08     ` Kanak Shilledar
2024-05-30 19:40 ` Jonathan Corbet

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='4oW9pC38sSYZn96BW8abMfVpDDCmG4MDHwwmL73o5bP-WyHAutJ5j2GrSU17MCSWOKufViNl4q2zZUmwmN40evP5OK3QiMnUn2hsgWCYhl4=@protonmail.com' \
    --to=kanakshilledar111@protonmail.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 \
    --cc=workflows@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