WKD proper behavior on fetch error
gnupg at eckner.net
Sun Jan 17 12:30:05 CET 2021
-----BEGIN PGP SIGNED MESSAGE-----
On Sun, 17 Jan 2021, Stefan Claas wrote:
> On Sun, Jan 17, 2021 at 10:51 AM Erich Eckner via Gnupg-users
> <gnupg-users at gnupg.org> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>> 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
> Well, Mailvelope, for example is a Browser based add-on with WKD support.
> Mailvelope can be used with services like Gmail, so that you don't need a MUA.
Ah, I see. That makes sense: integrate the keyring (and thus also a WKD
client) into the webmailer. OTOH: How do web-chat clients request SRV
records? Or do they simply not work with servers, who offer their
connection information via SRV?
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the Gnupg-users