WKD for GitHub pages
spam.trap.mailing.lists at gmail.com
Fri Jan 8 23:34:59 CET 2021
On Fri, Jan 8, 2021 at 11:27 PM André Colomb <andre at colomb.de> wrote:
> Hi Stefan,
> your key seems to work fine over that WKD setup.
> > Now Wiktor's WKD checker gives the proper
> > results in the first part, not sure why not in the
> > second part.
> You don't need the "Advanced" method if the direct one already works.
> They basically exist to provide flexibility for server admins to decide
> whether they want to issue a TLS certificate for the whole domain
> matching the e-mail address, or just serve the WKD stuff through a
> dedicated "openpgpkey" subdomain. The latter could be easier if the WKD
> webserver should be isolated from other things on the domain.
> In your setup, the valid TLS certificate for sac001.github.io is the
> only one you'll get, so the "Direct" method fits perfectly.
> Nice idea actually, but you'd have to check if GitHub actually allows
> such use for "arbitrary" data distribution.
> Good night.
as onbe could see from my previous reply, it does not work
with gpg4win and I tested it also under my Debian subsystem,
which didn't worked either. :-(
But (sorry to say this here on the GnuPG ML) good news is
I just tested it with an older version of sequoia-pgp and guess
what it works for me. :-)
sq wkd get stefan at sac001.github.io
-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: 3731 D9F8 1352 A24D F7E5 F33A 0885 70FC E611 8FD8
Comment: Stefan Claas <stefan at sac001.github.io>
-----END PGP PUBLIC KEY BLOCK-----
Regards and Good Night
More information about the Gnupg-users