[git] gnupg-doc - branch, master, updated. 0faf164596568dd0129e86c52dbe3aacee5175c9

by Kai Michaelis cvs at cvs.gnupg.org
Thu Aug 3 18:42:33 CEST 2017


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GnuPG website and other docs".

The branch, master has been updated
       via  0faf164596568dd0129e86c52dbe3aacee5175c9 (commit)
      from  ddb59c1fb16aeeb177561dae785450d52ae9107e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0faf164596568dd0129e86c52dbe3aacee5175c9
Author: Kai Michaelis <kai at gnupg.org>
Date:   Thu Aug 3 18:42:25 2017 +0200

    blog: wks with enigmail.

diff --git a/misc/blog.gnupg.org/20170803-web-key-in-enigmail.org b/misc/blog.gnupg.org/20170803-web-key-in-enigmail.org
new file mode 100644
index 0000000..c0a2f46
--- /dev/null
+++ b/misc/blog.gnupg.org/20170803-web-key-in-enigmail.org
@@ -0,0 +1,91 @@
+# Using the Web Key Service with Enigmail
+#+STARTUP: showall
+#+AUTHOR: Kai
+#+DATE: August 3, 2017
+
+** Using the Web Key Service with Enigmail
+
+Obtaining the public key of someone has always being a major pain point of
+using GnuPG. OpenPGP doesn't "outsource" trust management by using a PKI.
+Instead, it allows each user to decide whom to trust. This has the downside
+that we need to evaluate whether we can trust a new public key for each
+new communication partner. Until recently, there wasn't an automatic way to
+securely get the public key of someone you never communicated with.
+
+The [[https://tools.ietf.org/id/draft-koch-openpgp-webkey-service-03.html][Web Key Service]] and the new ~--auto-key-retrieve~ &
+~--auto-key-locate~ available in GnuPG 2.1.19 and beyond.
+
+*** Web Key Service
+
+The Web Key Service is a protocol to publish public OpenPGP keys via
+email and retrieve others' public keys using HTTPS. The advantage over
+HKPS is that every email provider maintains its own key
+server (called Web Key Directory, WKD) that is authoritative for all
+its users. This means that:
+
+1. There exists only one key server for a given email address. No need to ask
+   multiple servers as with HKPS.
+
+2. When publishing a public key using mail, WKD makes sure the sender is in
+   possession of the secret key.
+
+3. Email providers can (and should) make sure that only the owner of the
+   email account is able to publish a public key for it.
+
+Point three helps us with trust management. In case we trust the email
+provider of our communication partner, we can trust the key retrieved by WKD
+more than one from an HKPS based key server.
+
+#+CAPTION: Web key service protocol overview
+#+ATTR_HTML: :style max-width: 600px
+[[file:img/wks-schema.png]]
+
+*** Publish your public key to a Web Key Directory
+
+In order to use WKS you need a provider who supports it [fn:1]. After you
+configured the email account in Thunderbird you need to enable OpenPGP for
+it and generate a key pair.
+
+#+CAPTION: Enable the OpenPGP checkbox in the account settings.
+#+ATTR_HTML: :style max-width: 600px
+[[file:img/wks-account-settings.png]]
+
+Then, open the key management window and find your public key. Right clicking
+it opens the context menu. There, select the option to upload the public key
+to your provider's WKD.
+
+#+CAPTION: Context menu of the key management dialog.
+#+ATTR_HTML: :style max-width: 600px
+[[file:img/wks-key-mng.png]]
+
+After submission, the WKD will send an email to you asking to confirm the
+publication request. The subject line and body copy can be defined by the WKD
+but Enigmail will display a yellow bar above the message announcing it is a
+confirmation request. Clicking the button on the right will send the
+confirmation email to WKD.
+
+#+CAPTION: Enigmail adds a yellow bar to the confirmation request.
+#+ATTR_HTML: :style max-width: 600px
+[[file:img/wks-confirm-req.png]]
+
+After the email has been sent, your public key will be accessible to
+everybody.
+
+*** Receive others public key from a Web Key Directory
+
+Recent version of Enigmail receive missing public keys automatically form
+multiple sources, including WKD. Everybody who wants to send you an encrypted
+email will be able to do so without finding your public key manually first.
+
+This is a bit anticlimactic, but you can use the ~--auto-key-locate~
+option to retrieve your own public key from the WKD to see if it worked.
+
+~HOME=`mktemp -d` gpg2 --auto-key-locate wkd -e -r <your email address>~
+
+If GnuPG is able to retrieve the public key you will see a line that looks
+like that:
+
+~gpg: automatically retrieved '<your email address>' via WKD~
+
+[fn:1] As the time of writing only [[https://posteo.de/en][Posteo]] supports
+       WKS.
diff --git a/misc/blog.gnupg.org/img/wks-account-settings.png b/misc/blog.gnupg.org/img/wks-account-settings.png
new file mode 100644
index 0000000..4a6d47f
Binary files /dev/null and b/misc/blog.gnupg.org/img/wks-account-settings.png differ
diff --git a/misc/blog.gnupg.org/img/wks-confirm-req.png b/misc/blog.gnupg.org/img/wks-confirm-req.png
new file mode 100644
index 0000000..248a856
Binary files /dev/null and b/misc/blog.gnupg.org/img/wks-confirm-req.png differ
diff --git a/misc/blog.gnupg.org/img/wks-key-mng.png b/misc/blog.gnupg.org/img/wks-key-mng.png
new file mode 100644
index 0000000..002defe
Binary files /dev/null and b/misc/blog.gnupg.org/img/wks-key-mng.png differ
diff --git a/misc/blog.gnupg.org/img/wks-schema.png b/misc/blog.gnupg.org/img/wks-schema.png
new file mode 100644
index 0000000..b344903
Binary files /dev/null and b/misc/blog.gnupg.org/img/wks-schema.png differ

-----------------------------------------------------------------------

Summary of changes:
 .../20170803-web-key-in-enigmail.org               |  91 +++++++++++++++++++++
 misc/blog.gnupg.org/img/wks-account-settings.png   | Bin 0 -> 39786 bytes
 misc/blog.gnupg.org/img/wks-confirm-req.png        | Bin 0 -> 25065 bytes
 misc/blog.gnupg.org/img/wks-key-mng.png            | Bin 0 -> 26685 bytes
 misc/blog.gnupg.org/img/wks-schema.png             | Bin 0 -> 28318 bytes
 5 files changed, 91 insertions(+)
 create mode 100644 misc/blog.gnupg.org/20170803-web-key-in-enigmail.org
 create mode 100644 misc/blog.gnupg.org/img/wks-account-settings.png
 create mode 100644 misc/blog.gnupg.org/img/wks-confirm-req.png
 create mode 100644 misc/blog.gnupg.org/img/wks-key-mng.png
 create mode 100644 misc/blog.gnupg.org/img/wks-schema.png


hooks/post-receive
-- 
The GnuPG website and other docs
http://git.gnupg.org




More information about the Gnupg-commits mailing list