Received-SPF: pass (google.com: domain of linux-kernel+bounces-181897-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Date: Fri, 17 May 2024 09:08:30 +0000
To: Conor Dooley <conor@kernel.org>
From: 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: <hVKtRvWc18nNqYLUeYn_BDrvTbCR9tNZkgwvHBU3xGFdJjuNuQz-mT3o2QcsHFy4QyXOzwlnFXu_cM5pJxEhBeNa9jV_z6uZf83PO4OoCGk=@protonmail.com>
In-Reply-To: <20240516-tattered-rival-f443328b5971@spud>
References: <20240516-groin-slingshot-c3c3734d2f10@spud> <4oW9pC38sSYZn96BW8abMfVpDDCmG4MDHwwmL73o5bP-WyHAutJ5j2GrSU17MCSWOKufViNl4q2zZUmwmN40evP5OK3QiMnUn2hsgWCYhl4=@protonmail.com> <20240516-tattered-rival-f443328b5971@spud>
Feedback-ID: 26271244:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Sent with Proton Mail secure email.

On Thursday, May 16th, 2024 at 9:34 PM, Conor Dooley <conor@kernel.org> wro=
te:

> On Thu, May 16, 2024 at 04:00:10PM +0000, Kanak Shilledar wrote:
>=20
> > 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
> > > Revert commit 1d2ed9234c85 ("Documentation: process: Document
> > > suitability of Proton Mail for kernel development") as Proton disable=
d
> > > 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/=
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 ex=
ternal 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 Dir=
ectory
> > > -(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 w=
ill be
> > > -encrypted.
> > > -Unfortunately, Proton Mail does not provide a mechanism to disable t=
he
> > > -automatic encryption, viewing it as a privacy feature.
> > > -The automatic encryption feature is also enabled for mail sent via t=
he Proton
> > > -Mail Bridge, so this affects all outgoing messages, including patche=
s sent with
> > > -`git send-email`.
> > > -Encrypted mail adds unnecessary friction, as other developers may no=
t 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.
> >=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.
>=20
>=20
> I think that is probably reasonable, but I think writing the replacement
> text is up to someone who actually uses protonmail.

Alright! I will tryout hydroxide and roll out another patch in near future.
For now the patch looks good.

Reviewed-by: Kanak Shilledar <kanakshilledar111@protonmail.com>

Thanks and Regards,
Kanak Shilledar