von Firefox-Benutzer 13854774, vor 4 Jahren
Bewertet mit 5 von 5 Sternen
You may be able to use this https://dnscrypt.eu/ instead of hard-wiring Google in directly. Also, the Czech fellows who used to make DNSSEC Validator provided 2 IP4 and 2 IP6 machines to go with that. Other that supporting DNSSEC those are simply public DNS servers like Google's and there is nothing to enforce the use of their own plug-in. The addresses are in their documentation. (Actually, they may have a whole bunch more on the account of being people who run .cz TLD registry. AFAIK, the Czechs are the only TLD registry that support regular, documented version of DNSSEC, though there is a whole bunch more using some slightly hacked version of their own)
- von Asclepius, vor 2 JahrenBewertet mit 5 von 5 SternenThank you for this add-on. I just hope (since it isn't a "recommended" extension) that it is trustworthy. Aside from that concern, it serves its purpose. It would be nice if Firefox had built-in DNSSEC validation.
- von Firefox-Benutzer 15136226, vor 2 JahrenBewertet mit 4 von 5 SternenThis add on works well, however there are some issues as pointed out by other reviewers. I would like to note that ECDSAP256SHA256 works for me. It would also be nice if the add on verified https sites with DANE pinned certificates.
- von Firefox-Benutzer 14672905, vor 2 JahrenBewertet mit 4 von 5 SternenIt's great! And yes, would be even better once we have custom DNS, over TLS or not.
But this is a feature I have been waiting for so long, so I'm not going to hide my current feeling about this extension, it's awesome!!
- von Renaud, vor 3 JahrenBewertet mit 1 von 5 SternenUsing Cloudflare and Google for validation is not a good idea.
But also, validation fails for some kind of signatures, exemple: those using ECDSAP256SHA256.
- von Firefox-Benutzer 14514156, vor 3 JahrenBewertet mit 2 von 5 SternenI would give at least 4 stars, if it would use my local resolver instead of using google/cloudflare for DNS lookups.
Reason behind the downgrade:
1. it introduces a single point of failure:
if either of those sites can't answer, _ALL_ users of this extension (who have configured that site) can't use it, if it would use the local resolver and that failed it would be just the users of the local machine who experience that problem.
2. it is a privacy hazard:
a hacker needs to crack only a single (ok: two) machine(s) to get a complete log of who on this world tried to communicate with which web server....
if it would use the local configured resolver that _might_ still be a problem, depending on the configuration of said resolver, but mostly (I hope) those will contact multiple authoritative servers to walk from the root to the leaf containing the desired information and only the _last_ server will know which site I wanted to contact, but there it's irrelevant, since _that_ site knows it anyway.... (btw.: _THIS_ is the reason why I disabled this extension)
3. it can't verify local domains
according to 'dig' my own domains are DNSSEC enabled and working correctly, still your extension reports them as unsigned because there is no global glue record, as such while it is reachable from the world (via dyndns), the world doesn't see the DNSSEC information stored on my local dns-server.
- von Firefox-Benutzer 12739246, vor 4 JahrenBewertet mit 4 von 5 SternenGreat addon !
It just lacks the ability to set a custom DNS resolver, and the TLSA support.
Besides, the UI doesn't integrate well with a dark theme on Linux (KDE here, but I suspect it will be the same for another window manager), as the background of the tooltip gets its color from the system, and the font color seems to be hardcoded in black.
Oh, and I didn't find any link to the sourcecode. Is it available ? :)
- von Firefox-Benutzer 13816473, vor 4 JahrenBewertet mit 4 von 5 SternenBon début en remplacement du module DNSSEC/TLSA.
Pour quand la partie TLSA ?
Dommage que la validation se fasse avec les DNS de google.
- von 00dani, vor 4 JahrenBewertet mit 2 von 5 SternenFour stars for functionality, minus two because the implementation goes through Google. Yes, much the same as every other review so far - I'm actually writing this review to let you know that you don't actually need to trust any external HTTPS service to handle this!
Specifically, the Chrome version of DNSSEC/TLSA Validator, the extension you're clearly attempting to replicate, suffers from the same WebExtensions restrictions that modern Firefox does. Rather than trust an external service, however, they work around the issue through a WebExtensions feature called native messaging: a compiled binary is installed onto the system, which can do whatever it likes locally including make its own DNS queries, and then the WebExtension can ask that binary to check DNSSEC status when necessary.
Yes, it's a little bit of a hassle to install the necessary binary in the first place, since the browser won't install it automatically, but it's much more secure than trusting any external service - and it's no different to how the Chrome version of DNSSEC/TLSA Validator works right now.
I can confirm that Firefox supports this exact same approach, since I use several WebExtensions in Firefox this way (browserpass and bukubrow, specifically!). I don't know why the folks behind the DNSSEC/TLSA Validator haven't simply released a Firefox 57+ extension that uses native messaging, exactly like their existing Chrome extension, but it's definitely something you could do. :)