WKD proper behavior on fetch error

Ingo Klöcker kloecker at kde.org
Sun Jan 17 18:41:44 CET 2021

On Sonntag, 17. Januar 2021 10:48:17 CET Erich Eckner via Gnupg-users wrote:
> Hi all,
> On Thu, 14 Jan 2021, Werner Koch via Gnupg-users wrote:
> > On Thu, 14 Jan 2021 01:47, Ángel said:
> >> I understand this to mean it as "only use the direct method if the
> >> required sub-domain does not exist", with the SHOULD meaning that the
> >> direct method is not required (not sure why, I would have probably used
> > 
> > Right.  The subdomain is actually a workaround for SRV RR.  We can't
> > use the latter in browser based implementation and thus need to resort
> > to this hack.
> Forgive my ignorance, but can someone explain, what "browser based
> implementation" of WKD exists (or might exist) and/or why this is
> desirable?

https://openpgpjs.org/ supports WKD. OpenPGP.js is used by many web 
applications (see link). This is desirable to allow webmailers (and other web 
applications that support OpenPGP) to lookup OpenPGP keys via WKD.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20210117/a91fadcc/attachment.sig>

More information about the Gnupg-users mailing list