4 ms·

Actually it needs to use an HTTP API (because Web Extensions can't send actual DNS requests?): https://github.com/jessejanderson/skylink/blob/a698dd56eda26a6040

Actually it needs to use an HTTP API (because Web Extensions can't send actual DNS requests?): https://github.com/jessejanderson/skylink/blob/a698dd56eda26a6040861bbe3b8fa055da5ed090/content.js https://github.com/jessejanderson/skylink/blob/a698dd56eda26... and it looks like it's only resolving domains to DIDs, but not that the DID's owner accepted the domain; so you could make any of your domains point to anyone's DID. The extension would need to use ATP's new protocol to check it.

darnfish 3y ago
DNS over HTTP is still a DNS request
- reflexco 3y ago
  Whether it can technically be called a DNS request or not, this is a privacy leak for anyone who isn't already using Google as a DOH provider. So this should really be written on the extension page...
- progval 3y ago
  That seems to be a custom Google API, not DNS over HTTP(S). Request format is very different from what is specified in https://www.rfc-editor.org/rfc/rfc8484 https://www.rfc-editor.org/rfc/rfc8484 (/dns-query?dns= followed by raw DNS bytes). But sure, the implementation could easily be changed to use DoH