|
Size: 3521
Comment: slightly better phrasing to explain the difference between WKD and WKS. Upgrade for GnuPG 2.2. Update for mail users agents.
|
Size: 3535
Comment: Remove superfluous infos in the GnuPG wks tools entry.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 47: | Line 47: |
| * WKS server and client tools since GnuPG v2.1.14, see //[[https://gnupg.org/blog/20160830-web-key-service.html|how to run them in GnuPG's blog from 2016-08-30]]// or the [[WKS|Web Key Service page]]. <<FootNote(The server sends message pointing to https://gnupg.org/faq/wkd.html)>> |
* WKS server and client tools since GnuPG v2.1.14 which may help some providers (especially smaller ones) see the [[WKS|Web Key Service page]]. |
| Line 56: | Line 55: |
| * basic Kontact Mail/KMail support (part of EasyGpg2016) * basic Thunderbird support (part of EasyGpg2016) |
* basic (pre-release) Kontact Mail/KMail support (part of EasyGpg2016) * basic (pre-release) Thunderbird/Enigmail support (part of EasyGpg2016) * active consideration in planning for mutt * active consideration in planning for GpgOL (Gpg4win's Outlook Plugin) |
Much easier Email crypto, by fetching pubkey via HTTPS
How does it work?
As an email user, you just select the recipient(s) and can see that the email will be encrypted.
If you and your peers use email-providers offering this "web key service", it works by the first email. Otherwise encryption will start after you have exchanged some emails.
Technically your email client will automatically
- prepare for this by creating a crypto key for you and uploading it to your provider (or second best to public keyservers).
- sign all emails so others see that you are ready for crypto (unless you opt out)
- ask the mail provider of your recipients for their pubkeys.
An email-provider wanting to support privacy can
- provide a pubkey for users via HTTPS, called "web key directory" (WKD).
- allow each user's email client to automatically manage the pubkey that gets published by email, called "web key service" (WKS).
Details / Discussion
Pubkey Distribution Concept <- the (technical) details
- 2016-09-08 OpenPGP.conf presentation by Werner Koch: Abstract Slides.PDF
- 2016-09-08 OpenPGP.conf presentation by Bernhard Reiter, pages 21-24 Slides.ODP Slides.PDF
- 2016-09-09 OpenPGP-Schlüssel über HTTPS verteilen Golem news by Hanno Böck
- 2016-09-11 Spezifikation für die Verteilung von OpenPGP-Keys per HTTPS veröffentlicht Heise news by Johannes Merkert
- 2016-09-11 Anmerkungen zum Web Key Service gnupg-de@ by Werner Koch
- 2016-10-05 Draft 02 of the specs published (see details page linked above).
The elaborated proposal is a result of the EasyGpg2016 contract.
Implementations
Current GnuPG 2.2
- WKD lookup since v2.1.12, enabled by default since 2.1.23. Widespread rollout in 2017 because the old GnuPG 2.0 is scheduled end-of-life December 2017.
- WKS server and client tools since GnuPG v2.1.14 which may help some providers (especially smaller ones) see the Web Key Service page.
Mail User Agents
(Note that mail users agents using a modern GnuPG 2.2 will automatically do WKD requests via GnuPG. So they are WKD ready.)
Automatic pubkey bootstrapping (using the Web Key Service)
- basic (pre-release) Kontact Mail/KMail support (part of EasyGpg2016)
- basic (pre-release) Thunderbird/Enigmail support (part of EasyGpg2016)
- active consideration in planning for mutt
- active consideration in planning for GpgOL (Gpg4win's Outlook Plugin)
Mail Service Providers
- Posteo offers web key directory lookup and service. (Since 2016-12)
- (gnupg.org) Testing accounts by request for developers implementing WKS in Free Software MUAs.