o use only, which according to Wiktor's
WKD checker is properly set-up for my github.io page and most
important it is working with sequoia-pgp and Mailvelope etc. :-)
Best regards
Stefan
Best regards
Stefan
___
Gnupg-users mailing list
Gnupg-users@gnupg
On Tue, Jan 19, 2021 at 11:15 AM Werner Koch wrote:
>
> Stefan,
>
> It has been mentioned several time here that the use of the openpgpkey
> sub-domain is required to allow implementation of the Web Key Directory
> in browsers. This is a real world use case and pretty important for web
> mailers
Stefan,
It has been mentioned several time here that the use of the openpgpkey
sub-domain is required to allow implementation of the Web Key Directory
in browsers. This is a real world use case and pretty important for web
mailers like protonmail.
I would suggest that you put your energy on a
On Mon, 18 Jan 2021 17:12:56 +0100,
Stefan Claas wrote:
> I repeat here once again GitHub has a *valid* SSL cert.
You're right. github has a valid TLS certificate. But that valid TLS
certificate is not valid for openpgpkey.sac001.github.io. That's just
the way it is, sorry.
:) Neal
rposes, like one can see in my GitHub
> project folder, regarding Brave verification and one can see
> that a .well-known folder serves it's purpose for the direct
> method if one tries Wictor's fine WKD checker with
> stefan.sac001.github.io.
Well-known URIs were defined nearly 11 y
Hi Stefan,
On 18/01/2021 17.12, Stefan Claas via Gnupg-users wrote:
> I repeat here once again GitHub has a *valid* SSL cert.
You are right on that point. Absolutely right, seriously. It's
actually their web server configuration which is suboptimal. Those two
statements are universally true,
s Wiktor Kwapisiewicz's wkd checker:
>
> https://gitlab.com/wiktor-k/wkd-checker
> https://wkd.sequoia-pgp.org/
>
> This is more for checking a WKD setup than checking a WKD client.
>
> I'm sure he'd be open to issues for things that he missed.
>
> :) Neal
Hi Neal,
tha
On Sun, 17 Jan 2021 19:27:05 +0100,
Ángel wrote:
> I feel there is a need for a proper wkd test suite (as well as a
> clarifying on the draft itself the things that are coming up).
FWIW, there is Wiktor Kwapisiewicz's wkd checker:
https://gitlab.com/wiktor-k/wkd-checker
https://wkd.s
