|
Size: 2214
Comment: improved phrasing
|
Size: 3112
Comment: link to draft 02 fixed.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| * provide a pubkey for each user via ~HT~TPS | * provide a pubkey for users via ~HT~TPS |
| Line 19: | Line 19: |
| Line 32: | Line 34: |
| * 2016-09-11 [[https://www.heise.de/newsticker/meldung/Spezifikation-fuer-die-Verteilung-von-OpenPGP-Keys-per-HTTPS-veroeffentlicht-3317914.html|Spezifikation für die Verteilung von OpenPGP-Keys per HTTPS veröffentlicht//]] Heise news by Johannes Merkert | * 2016-09-11 //[[https://www.heise.de/newsticker/meldung/Spezifikation-fuer-die-Verteilung-von-OpenPGP-Keys-per-HTTPS-veroeffentlicht-3317914.html|Spezifikation für die Verteilung von OpenPGP-Keys per HTTPS veröffentlicht]]// Heise news by Johannes Merkert |
| Line 34: | Line 36: |
| //[[http://lists.gnupg.org/pipermail/gnupg-de/2016-September/000547.html|Anwerkungen zum Web Key Service]]// gnupg-de@ by Werner Koch | //[[http://lists.gnupg.org/pipermail/gnupg-de/2016-September/000547.html|Anmerkungen zum Web Key Service]]// gnupg-de@ by Werner Koch * 2016-10-05 Updated protocol specs published: [[https://tools.ietf.org/html/draft-koch-openpgp-webkey-service-02|Web Key Service (draft 02)]] |
| Line 37: | Line 40: |
== Implementations === GnuPG "modern" * WKD lookup experimental since v2.1.12 * WKS server and client experimental tools since v2.1.14, see //[[https://gnupg.org/blog/20160830-web-key-service.html|how to run them in GnuPG's blog vom 2016-08-30]]// or the [[WKS|Web Key Service page]]. === Mail User Agents * planned Kontact Mail/KMail support (part of EasyGpg2016) * planned Thunderbird support (part of EasyGpg2016) === Mail Service Providers * (planned for Sep/Okt 2016) [[https://posteo.de/en/|Posteo]] offering full implementation of "web key service". Posteo already implemented provisioning of pubkeys via HT~TPS. * (gnupg.org) Testing accounts by request for developers implementing WKS in Free Software MUAs. |
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 offering the "web key service" technically has to
- provide a pubkey for users via HTTPS
- allow each user's email client to automatically manage the pubkey that gets published by email.
Details / Discussion of the proposal
- EasyGpg2016/PubkeyDistributionConcept <- 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 Updated protocol specs published: Web Key Service (draft 02)
The elaborated proposal is a result of the EasyGpg2016 contract.
Implementations
GnuPG "modern"
- WKD lookup experimental since v2.1.12
- WKS server and client experimental tools since v2.1.14, see how to run them in GnuPG's blog vom 2016-08-30 or the Web Key Service page.
Mail User Agents
- planned Kontact Mail/KMail support (part of EasyGpg2016)
- planned Thunderbird support (part of EasyGpg2016)