Conversation
Conor Dooley
conor
kernel.org, protonmail & wkd: incompatibility
Show content
I ran afoul of this about a year ago, and have since noticed others having the same issue a few times since.
Kernel.org publishes the WKD for all developers who have kernel.org accounts, which is grand - but protonmail has a feature where it will automagically check for WKD and use it to encrypt messags.
Mailing lists & recipients without WKD will get the regular old copy of the mail.
To quote one of the other people that ran into this:
"they told me then that it's a super-pro
builtin feature that I can't disable 🤡"
That's the same answer I got & for both of us, the solution was just to leave protonmail.
Maintainers don't know about this & get "annoyed" with patch submitters & it is equally frustrating on the other side trying to figure out why your patchset has been encrypted...
The most recent occurance of this is here:
https://lore.kernel.org/all/Y6slQLto568WfmfZ@spud/
I feel like it should be documented somewhere that this issue exists, process/email-clients.txt doesn't seem quite right. Perhaps the patches documenting it should be CC the users@linux.kernel.org ML?
Kernel.org publishes the WKD for all developers who have kernel.org accounts, which is grand - but protonmail has a feature where it will automagically check for WKD and use it to encrypt messags.
Mailing lists & recipients without WKD will get the regular old copy of the mail.
To quote one of the other people that ran into this:
"they told me then that it's a super-pro
builtin feature that I can't disable 🤡"
That's the same answer I got & for both of us, the solution was just to leave protonmail.
Maintainers don't know about this & get "annoyed" with patch submitters & it is equally frustrating on the other side trying to figure out why your patchset has been encrypted...
The most recent occurance of this is here:
https://lore.kernel.org/all/Y6slQLto568WfmfZ@spud/
I feel like it should be documented somewhere that this issue exists, process/email-clients.txt doesn't seem quite right. Perhaps the patches documenting it should be CC the users@linux.kernel.org ML?
1
7
6
re: kernel.org, protonmail & wkd: incompatibility
Show content
@broonie
> it’s a lot of hassle to arrange to view the encrypted message
If that fella replies to me, I'll probably have to go configure my mailer properly to be able to read it.
> mail-clients seems like the right place?
I felt that it may not be the right spot since the issue is not client specific, but an issue with the provider full-stop. I'd expect people to stop reading after "General Preferences" if they intend using git send-email.
I checked the docs again, and the new styling that was applied for v6.2-rc1 does actually enumerate all of the page headings, so the per client documentation is harder to overlook now. With v6.1.y and prior, it'd be very easy to overlook.
I guess I'll add a comment there & CC the users list...
> it’s a lot of hassle to arrange to view the encrypted message
If that fella replies to me, I'll probably have to go configure my mailer properly to be able to read it.
> mail-clients seems like the right place?
I felt that it may not be the right spot since the issue is not client specific, but an issue with the provider full-stop. I'd expect people to stop reading after "General Preferences" if they intend using git send-email.
I checked the docs again, and the new styling that was applied for v6.2-rc1 does actually enumerate all of the page headings, so the per client documentation is harder to overlook now. With v6.1.y and prior, it'd be very easy to overlook.
I guess I'll add a comment there & CC the users list...
0
0
0
K. Ryabitsev
monsieuricon
re: kernel.org, protonmail & wkd: incompatibility
Show content
@conor Eek. Protonmail is just not very good for this kind of work, period -- I see zero reason why you would want to use it for anything other than communicating with someone else who has a protonmail account.
1
0
0
Conor Dooley
conor
re: kernel.org, protonmail & wkd: incompatibility
Show content
@monsieuricon bad it may be, but automagical encryption like that to people who are not even protonmail users is not really what would be expected. If I was a drive-by contributor, I would expect my proton account to just work.
0
0
0