Some tests with Firefox (video)

Midimusicman79 I hope it is useful for you.

Edited by hamluis, 04 June 2023 - 08:03 AM.
Moved from Web Browsing to Tips/Tricks - Hamluis.

And...what might be the purpose/results of such tests?

Louis

Increased privacy,increased security.

Thank you, Sampei_Nihira!

And yes, upon visiting WebRTC Leak Test - BrowserLeaks, as my screenshot shows, I already have most, if not all, the same results.

So, I did change my relevant media.peerconnection.enabled=false setting in Mozilla Firefox - about:config.

Each test in the video should be not similar (similar is not good), but identical.

Thank you, Sampei_Nihira!

However, on the Ping Spotter Test in Mozilla Firefox, I get this result: Beacon API Status Request Sent 🔥, but the other tests are blocked.

So, I would like to ask you, what are the pros and cons of changing the Beacon.enabled=false setting in Firefox - about:config.

On the Encrypted Client Hello (ECH) test, I get this result: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

On the Canvas Fingerprinting Test, I get this result: Uniqueness of 99.97% (50 of 181189 user agents have the same signature), and your web browser is Firefox, and your operating system is Windows.

On the WebGL Browser Report Test, I get this result: This browser supports WebGL ✔ True, and This browser supports WebGL 2 ✔ True.

On the Geolocation API test, I get this result: Origin Permissions ? "prompt" – you ask when browserleaks.com tries to request your location...,

...Global Permissions × "denied" – you don't allow third-party websites to request your location Geolocation API API Status ✔ Your browser supports Geolocation API.

On the Content Filters and Proxy Detection Test, I get this result: Subscriptions ✔ Detected 9 Filters: 8 General, 1 Regional.

And on the SSL/TLS Client Test, I get this result: HTTP User-Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0.

Study in the various parts this famous user.js:

https://github.com/arkenfox/user.js/blob/master/user.js

Edited by Sampei_Nihira, 04 June 2023 - 01:37 PM.

You probably already know this, but Mozilla Firefox, version 119, which recently was published, features Encrypted Client Hello (ECH).

The browser's Release Notes state, "Encrypted Client Hello (ECH) is now available to Firefox users, delivering a more private browsing experience.

ECH extends the encryption used in TLS connections to cover more of the handshake and better protect sensitive fields. Read more about the launch of ECH on Mozilla Distilled."

On the Encrypted Client Hello (ECH) test, I get this result: SSL_ECH_OUTER_SNI: cover.defo.ie, SSL_ECH_INNER_SNI: defo.ie, and SSL_ECH_STATUS: success .

Out of curiosity, I decided to test all my Chromium-based browsers with the Encrypted Client Hello (ECH) test, and here are the results:

In Microsoft Edge Chromium, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Google Chrome, I get this: SSL_ECH_OUTER_SNI: cover.defo.ie, SSL_ECH_INNER_SNI: defo.ie, and SSL_ECH_STATUS: success .

In Opera, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Sleipnir, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Vivaldi, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Brave Chromium, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Chromium Stable, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Opera GX, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Mozilla Firefox Portable, I get this: SSL_ECH_OUTER_SNI: cover.defo.ie, SSL_ECH_INNER_SNI: defo.ie, and SSL_ECH_STATUS: success .

In Vivaldi Portable, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Sleipnir Portable, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Brave Portable, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

In Google Chrome Portable, I get this: SSL_ECH_OUTER_SNI: cover.defo.ie, SSL_ECH_INNER_SNI: defo.ie, and SSL_ECH_STATUS: success .

In Opera Portable, I get this: SSL_ECH_OUTER_SNI: NONE, SSL_ECH_INNER_SNI: NONE, and SSL_ECH_STATUS: not attempted .

When Encrypted Client Hello (ECH) first became available in Mozilla Firefox version 85 on January 7, 2021, it was only experimental or a draft.

In the above article, it says, "Though we recommend that users wait for ECH to be enabled by default, some may want to enable this functionality earlier."

That is one difference between you and me because I waited until ECH was enabled by default, but you enabled this functionality earlier.

Feature: TLS Encrypted Client Hello (ECH) became generally available in Chromium-based browsers version 117, and I waited for that as well.

As mentioned, Encrypted Client Hello (ECH) is nowadays apparently only available by default in Google Chrome, but you enabled this functionality earlier in Microsoft Edge Chromium.

I have decided to wait for that functionality to become available by default in my other Chromium-based browsers because I do NOT enjoy enabling features in chrome://flags/.

The Encrypted Client Hello (ECH) setting in Google Chrome is configurable via chrome://flags/#encrypted-client-hello.

And in Microsoft Edge Chromium via the --enable-features=EncryptedClientHello Command Line switch and via edge://flags/#dns-https-svcb and edge://flags/#use-dns-https-svcb-alpn.