PGP drie

In earlier posts I describe how I have set up GPG on Kmail and K9mail. I discovered that Kleopatra is included in gpg4win, and yesterday I used it to import my keys and succesfully set up Thunderbord/Enigmail this way. I also discovered that Mailvelope, the browser plugin which allows you to use PGP in webmail seems to use openpgp.js, and does not in fact require any extra client, which is of course superior UX to the whole deamon/manager/client thing that you do for desktop software. Encryption should be a library! I wrote seems to, because the Mailvelope website does not mention it uses openpgp.js.

Strangely, Enigmails documentation is quite clear and recommends gpg4win, but according to a message on Debian bugs it does include openpgp.js. Can you still follow? I certainly don’t!

Also, I discovered that although K9mail “improved” its UX as to how the status of encryption is shown, it shows a non-green lock icon with a cross sometimes, which is not on that website explaining the new icons! Tapping the icons gives the cryptic (haha!) message that the message is encrypted but not end to end (how is that even possible?). Checking these mails with Kmail shows these messages are encrypted but not signed (why is that even possible?) which is not not encrypted, and not explained anywhere in K9mails UI or docs… Man o man…

Enfin! I set PGP up on a variety of clients and operating systems, for my and my partner, and I am happy ‘s all good now. I know now how the mail concepts work, how to configure some mainstream clients and I can now send and recieve encrypted messages! I will agree with any and all UX critiques to PGP though: it leaves something to be desired.

You may find my public key on various keyservers and also on right here: pgp_pub.asc.