Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

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

  • 3 antwoorde
  • 1 het hierdie probleem
  • 1 view
  • Laaste antwoord deur Scott S

Scott S
Scott S
more options

DoH is being configured by default in the US in the near future. While a great tool, 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!

DoH is being configured by default in the US in the near future. While a great tool, 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!

All Replies (3)

Scott S
Scott S Vraag-eienaar
more options

In looking at the other responses from that user, that is a spam phone number and unrelated to Firefox

Gewysig op deur Scott S

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Hi Scott, I think your suggestion may be over my head!

I do see a page for how companies qualify as a trusted resolver for inclusion in Firefox, but that might not be needed:

https://wiki.mozilla.org/Security/DOH-resolver-policy

Instead it sounds as though if Firefox cannot currently use a client certificate to connect to a resolver for DoH, that needs to be added.

I'm not sure where would be the best place to work out the details of that. Maybe

https://discourse.mozilla.org/c/firefox-development

Or you could file a new but, although new feature requests tend to get a low priority if they aren't part of a roadmap:

Scott S
Scott S Vraag-eienaar
more options

Thanks! Yeah, the resolver policy page is more about companies that want to provide the service to consumers. This is more about companies doing it for their employees to get consistancy wherever laptops are in the world.

I'll try discourse next. That might get some results or people interested.

Thanks!