forked from Mirrors/keyoxide-web
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
This commit is contained in:
parent
efa31cc844
commit
125d6d9924
1 changed files with 1 additions and 1 deletions
|
@ -22,7 +22,7 @@
|
||||||
|
|
||||||
<p>While not necessary if the Direct setup works, there is a second setup to make WKD work: the Advanced setup. The paths needed are:</p>
|
<p>While not necessary if the Direct setup works, there is a second setup to make WKD work: the Advanced setup. The paths needed are:</p>
|
||||||
|
|
||||||
<p><strong>https://openpgpkey.domain.org/.well-known/openpgpkey/policy</strong>: this is an empty file</p>
|
<p><strong>https://openpgpkey.domain.org/.well-known/openpgpkey/domain.org/policy</strong>: this is an empty file</p>
|
||||||
<p><strong>https://openpgpkey.domain.org/.well-known/openpgpkey/domain.org/hu/LOCALPART</strong>: this is the binary public key (so NOT ASCII armored)</p>
|
<p><strong>https://openpgpkey.domain.org/.well-known/openpgpkey/domain.org/hu/LOCALPART</strong>: this is the binary public key (so NOT ASCII armored)</p>
|
||||||
|
|
||||||
<p>Indeed, quite similar to the Direct setup, except for the <strong>openpgpkey</strong> subdomain and the additional <strong>domain.org</strong> in the path of the public key.</p>
|
<p>Indeed, quite similar to the Direct setup, except for the <strong>openpgpkey</strong> subdomain and the additional <strong>domain.org</strong> in the path of the public key.</p>
|
||||||
|
|
Loading…
Reference in a new issue