Received-SPF: pass (google.com: domain of linux-kernel+bounces-181289-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Thu, 16 May 2024 17:04:16 +0100
From: Conor Dooley <conor@kernel.org>
To: Kanak Shilledar <kanakshilledar111@protonmail.com>
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"
Message-ID: <20240516-tattered-rival-f443328b5971@spud>
References: <20240516-groin-slingshot-c3c3734d2f10@spud>
 <4oW9pC38sSYZn96BW8abMfVpDDCmG4MDHwwmL73o5bP-WyHAutJ5j2GrSU17MCSWOKufViNl4q2zZUmwmN40evP5OK3QiMnUn2hsgWCYhl4=@protonmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="M4UZhHp/KDapPJjU"
Content-Disposition: inline
In-Reply-To: <4oW9pC38sSYZn96BW8abMfVpDDCmG4MDHwwmL73o5bP-WyHAutJ5j2GrSU17MCSWOKufViNl4q2zZUmwmN40evP5OK3QiMnUn2hsgWCYhl4=@protonmail.com>


--M4UZhHp/KDapPJjU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 16, 2024 at 04:00:10PM +0000, Kanak Shilledar wrote:
> On Thursday, May 16th, 2024 at 9:05 PM, Conor Dooley <conor@kernel.org> w=
rote:
>=20
> > From: Conor Dooley conor.dooley@microchip.com
> >=20
> >=20
> > 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
> >=20
> > Signed-off-by: Conor Dooley conor.dooley@microchip.com
> >=20
> > ---
> >=20
> > I tried to find the stuff on social.korg to provide a link
> > but could not.
> >=20
> > CC: kanakshilledar111@protonmail.com
> > CC: Konstantin Ryabitsev konstantin@linuxfoundation.org
> >=20
> > CC: Mark Brown broonie@kernel.org
> >=20
> > CC: Jonathan Corbet corbet@lwn.net
> >=20
> > 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(-)
> >=20
> > diff --git a/Documentation/process/email-clients.rst b/Documentation/pr=
ocess/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 exte=
rnal editor.
> >=20
> > 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 Direc=
tory
> > -(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 ac=
counts.
> > -As a result, emails sent using Proton Mail to kernel.org addresses wil=
l 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 m=
ail
> > -clients may encrypt responses to encrypted mail for all recipients, in=
cluding
> > -the mailing lists.
> > -Unless a way to disable this "feature" is introduced, Proton Mail is u=
nsuited
> > -to kernel development.
>=20
> 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.

I think that is probably reasonable, but I think writing the replacement
text is up to someone who actually uses protonmail.

--M4UZhHp/KDapPJjU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZkYugAAKCRB4tDGHoIJi
0omAAQD2PDht18QafEYRX8KcAkFSW+u0xgTPRkv1jW67OHnXUQD/b7l2pDkiHGJO
H0NRHTXedMoiytMxuVkw1tu7zM96SwE=
=qAQV
-----END PGP SIGNATURE-----

--M4UZhHp/KDapPJjU--