Web lists-archives.com

Re: Trusted Recursive Resolver

On 08/06/2018 03:34 PM, WaltS48 wrote:
On 8/6/18 3:18 PM, Caver1 wrote:
On 08/06/2018 03:05 PM, Christian Riechers wrote:
On 08/06/2018 06:38 PM, Caver1 wrote:
On 08/06/2018 10:52 AM, Caver1 wrote:
I don't know in which release Mozilla is planning to have Trusted
Recursive Resolver or even if it is a given.
Maybe it is in a nightly now. I don't know as I don't run nightlies.
My question is is Mozilla going to let a user disable Trusted
Recursive Resolver?

I should have stated it that Trusted Recursive Resolver makes you use
the DNS server Mozilla wants while using Firefox.

It's fascinating to see how some people seem to have nothing better to
do than spreading FUD.

Not everyone sees this as fud. Remember the last time made one of their features as opt-out and not opt-in. That wasn't anything as consequential as this.
They got an extreme amount of flac for it.

As far as I know it is a study and opt-in.

As I stated above i didn't know if it was a given. In otherwords if it will go beyond the testing stage. What I have read is Mozilla is planning on using TTR at some point in the future. and if so....does anyone know. There are people here that know more than I do. Hence the question.

Typing about:studies into the Address Bar shows;

Complete•Mozilla is running a series of studies to evaluate a service that keeps DNS providers from collecting and sharing your browsing history. All users in the study will receive a notification. When a study is active, Firefox will automatically use Cloudflare’s secure DNS over HTTPS. This study will use the Cloudflare resolver in addition to the DNS selected by a user or their ISP in order to compare approaches. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1446404";

I had to "Change network.trr.mode to 2 to enable DoH. This will try and use DoH but will fallback to insecure DNS under some circumstances like captive portals.  (Use mode 5 to disable DoH under all circumstances.)"

The Value was "0", then I had to select a server and add it as a Value to "network.trr.uri".

I'm happy you found the method to disable it to your satisfaction.

I had no question about what you stated above.
The question still stands when fully implemented. Will there be an opt-out? When I clearly stated that it may not happen. But I do find that unlikely. which I didn't state before to stay away from conjecture. If you don't know then why respond at all instead of making it look like I''m bashing Mozilla. I never said I disabled it. I just stated how. Buy finding out how I found out that it is also in 61.01.

general mailing list