From 2a0c6b72a5c8d1026b2387831cf4d163ef15ac08 Mon Sep 17 00:00:00 2001 From: Katharina Fey Date: Thu, 11 Jul 2019 23:18:42 +0100 Subject: Updating the GPG article with notes provided via e-mail --- content/blog/108_usable_gpg.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/content/blog/108_usable_gpg.md b/content/blog/108_usable_gpg.md index 2ef3355..350f352 100644 --- a/content/blog/108_usable_gpg.md +++ b/content/blog/108_usable_gpg.md @@ -47,13 +47,20 @@ You need to create a `.well-known/openpgpkey` directory on your server. In this directory, place a `policy` file. This can be zero-length, but is used to check for WKD capability. Next, create a `hu` folder inside it -(no idea what this stands for...) +(no idea what this stands for... +— as pointed out by an attentive reader, it stands for [hashed-userid]) + +[hashed-userid]: https://www.gnupg.org/blog/20160830-web-key-service.html Next, take the prefix of your e-mail address (i.e. in `kookie@spacekookie.de`, this would be `kookie`), hash it with SHA-1 and then encode the output with z-base-32. You can use [this][cryptii] convenient encoding website. +**Edit:** Also pointed out by a reader, you can actually use +`gpg --with-wkd -l ` to display your hashed User ID +instead of using an external resource for this. + [cryptii]: https://cryptii.com/pipes/z-base-32 Export the **binary** version of your pubkey (so without `-a`) -- cgit v1.2.3