Latest comment: 26 August 2020 by Archaid in topic Re: How a user can disable connection tests in /Firefox/Privacy
Re: How a user can disable connection tests in /Firefox/Privacy
Hi, please add references to the content you added to Firefox/Privacy, they are not visible to other users from the edit summary.
- Hi Lahwaacz, woops my bad, I thought it would be automatic, but having looked at what I did, I edited the start of the Edit summary from
/* References */to
/* Added */. Maybe that's the reason it didn't work. This is what I wrote in the Edit summary.
/* Added */ A problem that I discovered while running a packet sniffer and loading Firefox. On startup in order to get the IP address of firefox.com,
it seems that mozilla.cloudflare-dns.com is used, despite setting other DNS servers as per another section. This suggests that the cloudflare-dns.com is hard-coded by Mozilla into this feature. Other resources/examples here and here
- BTW part of the above may be incorrect. I might make this section more explicit, because simply deleting the
network.trr.uriand leaving a collection of resolvers in
network.trr.resolversDOES NOT WORK. Firefox will silently and automatically reset the former to the Cloudflare URI! The effect that I'm looking for is for Firefox to use a couple of DNS servers chosen at random from a list. I may edit the section when I've identified how to do this.
- —This unsigned comment is by Archaid (talk) 09:10, 26 August 2020. Please sign your posts with ~~~~!
- Actually what I meant here is that you should put the references/URLs in the page itself to make them visible to the readers of the page. Readers will not go through the history of the page to see when was each section/paragraph added.
- The text between
*/in the edit summary is the name of the section you edited and generates an automatic link from the history page to the main page. It does not have any other function.
- -- Lahwaacz (talk) 11:59, 26 August 2020 (UTC)
- Thanks for the info, I'll do that soon, yes.
- To follow up, my thinking above is not how TRR works. In fact, Firefox silently resets the
network.trr.urito Cloudflare if it's blank. That's the reason Firefox talked to Cloudflare on startup. The variable
network.trr.resolversonly populates a drop-down selection in the Network > Connection Settings pane for the user to manually select. A user must explicitly choose and use only one DNS server at any one time. Putting aside any third-party extensions, its unlikely a user will do this and limit the amount of DNS traffic they send to any single DNS server for privacy/anti-fingerprinting reasons. Unfortunate.
- Archaid (talk) 22:56, 26 August 2020 (UTC)