From 125d6d9924f470bd5ad99078bdcd406e7a243e7e Mon Sep 17 00:00:00 2001 From: Benoit Joly Date: Sat, 18 Jul 2020 22:08:46 -0400 Subject: [PATCH] fixing WKD advanced policy file location according to specs According to section "4.5. Policy Flags", the policy file must be located at the location WELLKNOWN/policy. In section "4. Web KeyDirectory Update Protocol", WELLKNOWN is defined as followed for the advanced method: https://openpgpkey.example.org/.well-known/openpgpkey/example.org The guide has the policy path wrong (one level up), in .well-known/openpgpkey instead of .well-known/openpgpkey/domain.org --- views/guides/web-key-directory.content.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/views/guides/web-key-directory.content.php b/views/guides/web-key-directory.content.php index 92c6003..ecc5059 100644 --- a/views/guides/web-key-directory.content.php +++ b/views/guides/web-key-directory.content.php @@ -22,7 +22,7 @@

While not necessary if the Direct setup works, there is a second setup to make WKD work: the Advanced setup. The paths needed are:

-

https://openpgpkey.domain.org/.well-known/openpgpkey/policy: this is an empty file

+

https://openpgpkey.domain.org/.well-known/openpgpkey/domain.org/policy: this is an empty file

https://openpgpkey.domain.org/.well-known/openpgpkey/domain.org/hu/LOCALPART: this is the binary public key (so NOT ASCII armored)

Indeed, quite similar to the Direct setup, except for the openpgpkey subdomain and the additional domain.org in the path of the public key.