WKD for GitHub pages
spam.trap.mailing.lists at gmail.com
Sat Jan 9 20:08:09 CET 2021
On Sat, Jan 9, 2021 at 7:27 PM Ingo Klöcker <kloecker at kde.org> wrote:
> On Samstag, 9. Januar 2021 15:43:14 CET Stefan Claas via Gnupg-users wrote:
> > Example: If I would be the host master of the domain bund.de with it's
> > many subdomains and authorities would request that WKD, as an
> > inexpensive inhouse option, has to be set-up...
> > IMHO that would be the same case, if I am not mistaken.
> No, it's not.
> Even if there's foo.bund.de, then there wouldn't be openpgpkey.foo.bund.de
> (unless foo.bund.de sets up the advanced variant of WKD).
> The problem with GitHub pages is apparently that openpgpkey.sac001.github.io
> resolves to an IP address (well, actually multiple addresses):
> $ host openpgpkey.sac001.github.io
> openpgpkey.sac001.github.io has address 184.108.40.206
> openpgpkey.sac001.github.io has address 220.127.116.11
> openpgpkey.sac001.github.io has address 18.104.22.168
> openpgpkey.sac001.github.io has address 22.214.171.124
sac001.github.io has address 126.96.36.199
sac001.github.io has address 188.8.131.52
sac001.github.io has address 184.108.40.206
sac001.github.io has address 220.127.116.11
works as well and why can sequoia-pgp handle this and not GnuPG,
or gpg4win? Couldn't they not fall back then as well to the direct method?
More information about the Gnupg-users