Open Bug 1619781 Opened 5 years ago Updated 2 years ago

Can DNS over HTTPS settings be fixed to provide support for authentication via client certificates?

Categories

(Core :: Networking: DNS, enhancement, P3)

73 Branch
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: github, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged][trr])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

I built a private DNS over HTTPS server and configured SSL mutual authentication via client certificates. I then pointed Firefox at the service.

Actual results:

It didn't work. Firefox doesn't appear to support authentication for DNS over HTTPS.

Expected results:

Was told to try posting this here… Originally posted it over all Firefox community support…

DoH is a big initiative for Mozilla right now and soon will be enabled by default in the US. While a great tool for privacy, I believe the companies can benefit as well. Most users have laptops. Laptops leave the confines of the office regularly. Why not have laptops configured so that they point to a companies DNS infrastructure when not in the office? The benefit would be that any filtering/monitoring being done via DNS no longer is limited to when devices are on the company network!

This would require companies exposing DNS to the internet which is considered a bad idea. DNS will expose internal secrets and let the bad guys probe the architecture of the network for information they can use later. Adding authentication to the DoH solution would allow companies to leverage their internal certificate infrastructure and already deployed client certificates to protect that DNS information.

TLS mutual auth via client certificates is part of the SSL/TLS protocol already in use by DoH and there is nothing in the RFC to prevent this from being a possibility.

Is this something that can be added to the roadmap (or is it already on the roadmap)?

Thanks!

Priority: -- → P3
Whiteboard: [necko-triaged][trr]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.