aboutsummaryrefslogtreecommitdiff
path: root/content/blog/108_usable_gpg.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/blog/108_usable_gpg.md')
-rw-r--r--content/blog/108_usable_gpg.md9
1 files changed, 8 insertions, 1 deletions
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...)
+(<strike>no idea what this stands for...</strike>
+— 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 <email>` 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`)