-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
general.buildID.override + dom.battery.enabled #485
Comments
yes UA is sent with every request regardless of JS |
let's do it ... #486 |
You have mentioned /* 0804: limit history leaks via enumeration (PER TAB: back/forward) - PRIVACY
* This is a PER TAB session history. You still have a full history stored under all history
* default=50, minimum=1=currentpage, 2 is the recommended minimum as some pages
* use it as a means of referral (e.g. hotlinking), 4 or 6 or 10 may be more practical ***/
user_pref("browser.sessionhistory.max_entries", 10); is there any security/privacy implications that prevents the following to be set as 10?: /* 1020: disable the Session Restore service completely
* [WARNING] [SETUP] This also disables the "Recently Closed Tabs" feature
* It does not affect "Recently Closed Windows" or any history. ***/
user_pref("browser.sessionstore.max_tabs_undo", 10); Thx and cheers |
But... don't we sanitize this by the current shutdown settings?: /*** 2800: SHUTDOWN [SETUP]
You should set the values to what suits you best.
- "Offline Website Data" includes appCache (2730), localStorage (2710),
Service Worker cache (2740), and QuotaManager (IndexedDB (2720), asm-cache)
- In both 2803 + 2804, the 'download' and 'history' prefs are combined in the
Firefox interface as "Browsing & Download History" and their values will be synced
***/
user_pref("_user.js.parrot", "2800 syntax error: the parrot's bleedin' demised!");
/* 2802: enable Firefox to clear history items on shutdown
* [SETTING] Privacy & Security>History>Clear history when Firefox closes ***/
user_pref("privacy.sanitize.sanitizeOnShutdown", true);
/* 2803: set what history items to clear on shutdown
* [SETTING] Privacy & Security>History>Clear history when Firefox closes>Settings
* [NOTE] If 'history' is true, downloads will also be cleared regardless of the value
* but if 'history' is false, downloads can still be cleared independently
* However, this may not always be the case. The interface combines and syncs these
* prefs when set from there, and the sanitize code may change at any time ***/
user_pref("privacy.clearOnShutdown.cache", true);
user_pref("privacy.clearOnShutdown.cookies", true);
user_pref("privacy.clearOnShutdown.downloads", true); // see note above
user_pref("privacy.clearOnShutdown.formdata", true); // Form & Search History
user_pref("privacy.clearOnShutdown.history", true); // Browsing & Download History
user_pref("privacy.clearOnShutdown.offlineApps", true); // Offline Website Data
user_pref("privacy.clearOnShutdown.sessions", true); // Active Logins
user_pref("privacy.clearOnShutdown.siteSettings", false); // Site Preferences |
Understood, thank you. /* 0862 */ user_pref("places.history.enabled", false); Thanks ❤️ and sorry for hijacking the topic. |
only if you don't have /* 1021: disable storing extra session data
* extra session data contains contents of forms, scrollbar positions, cookies and POST data
* define on which sites to save extra session data:
* 0=everywhere, 1=unencrypted sites, 2=nowhere ***/
user_pref("browser.sessionstore.privacy_level", 2); |
nope, the buildID in the UA is (and has been for a long time) always |
Doesn't comply with what I see. user_pref("browser.sessionstore.privacy_level", 2); if I close the tab and check cookie storage its still there and then restore it with |
Hmm interesting. It's probably because there are 2 kinds of cookies, session and "permanent" (ie with an expire date). I assume FF keeps permanent ones in cookies.sqlite and session cookies in sessionstore.jsonlz4. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie
I guess the bold part is where If you want to know exactly what's stored in sessionstore.jsonlz4 you can try if dejsonlz4 is able to decompress it and look at its content. Close the browser before you do, though, and I'd recommend to copy the file before you tamper with it. We should probably change the line |
Does general.buildID.override still work? |
Yes but only if mozilla-release == FF62 at the moment |
we should enable this for non-RFP users. It doesn't conflict with RFP so there's really no reason not to enable it, IMHO.
see
buildID
@ https://browserleaks.com/javascript with and w/o RFP.gecko.buildID
doesn't exist anymore since at least FF52: compare DXR ESR45 vs ESR52dom.battery.enabled
- it's not deprecated and shouldn't be under 9999. IDK a good reason why we shouldn't actively disable it IMO. Let's move it back into the active part of the user.jsjust my 2 cents
The text was updated successfully, but these errors were encountered: