public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: corbet@lwn.net, Conor Dooley <conor.dooley@microchip.com>,
	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: Thu, 29 Dec 2022 13:13:04 +0000	[thread overview]
Message-ID: <Y62SYKyhE+hPX5b9@sirena.org.uk> (raw)
In-Reply-To: <20221228000330.3971104-1-conor@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

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>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-12-29 13:12 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
2022-12-28 13:06   ` Conor Dooley
2022-12-29 13:13 ` Mark Brown [this message]
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=Y62SYKyhE+hPX5b9@sirena.org.uk \
    --to=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