New Update Disable Visited Links, Disable IndexedDB - Privacy Add-ons

[Prorootect]

Disable Visited Links, Disable IndexedDB - Privacy Add-ons

Disable Visited Links by Chris Antaki
Disable Visited Links – Add-ons for Firefox
- Not compatible with Firefox Quantum
This plugin cleanly disables visited link styles.
Did you know that visited link styles allow websites to elicit web history? [1]
This plugin cleanly disables visited link styles.

[1] http://lcamtuf.coredump.cx/css_calc/

Source code is available here: https://github.com/ChrisAntaki/visited-links-firefox


--------------------------------------------------------

Disable IndexedDB by Chris Antaki
Disable IndexedDB – Add-ons for Firefox
- Not compatible with Firefox Quantum
Disables IndexedDB consistently.
This plugin disables IndexedDB, with the goal of enhancing privacy by making your browser a little harder to uniquely fingerprint. Please be warned, websites that depend on IndexedDB might not work when this plugin is enabled. You can always click the icon to disable/enable the plugin. Green means IndexedDB is disabled, and red means it's available for websites to use. By default, this plugin will enable itself every time Firefox boots up. If you'd like the disabled status to persist across reboots, there's an option allowing that in the plugin preferences screen. That about covers it all. Hope you enjoy the plugin.

Source code is available here: https://github.com/ChrisAntaki/disable-indexeddb

If there's an issue with the plugin, please let me know: https://github.com/ChrisAntaki/disable-indexeddb/issues

"When Private Browsing mode is used, it is possible for a web worker to write persistent data to IndexedDB and fingerprint a user uniquely. IndexedDB should not be available in Private Browsing mode and this stored data will persist across multiple private browsing mode sessions because it is not cleared when exiting."
- link with this description here: Security vulnerabilities fixed in Firefox 57.0.1


These two add-ons I've downloaded - are very light...

 

[AlanOstaszewski]

You can deactivate IndexedDB by this setting in about:config: dom.indexedDB.enabled but disabling it is highly unrecommended because uBlock needs it.
The first addon is maybe useful but the Tor Browser doesn't has a history and so I don't need this addon.

 

[Prorootect]

Thank you askalan to rapport this IndexedDB problem in uBlock O. - from Firefox 57 and more.

From 1313401 - Background Page LocalStorage is cleared along with site storage :

voltron
Comment 21 •
5 months ago

I think the whole bunch of problems with IndexedDB and localStorage related to WebExtensions could be summarized into a simple specification:

"WebExtension *Background page* can use IndexedDB and window.localStorage always. Contents of these storages are deleted only when the user removes the extension or when the extension code itself decides to clear them by calling related APIs."

In other words, IndexedDB and window.localStorage for the WebExtension _background page_ (<-- this is the key) should work regardless of any cookie settings, remember history settings, "clear history when Firefox closes" settings or Private Browsing mode. Those should not limit what the background page can do.

...and from [Support] uBlock Origin

orwell2017
Sep '17
uBlock Origin webext does not work for privacy conscious people who block
cookies by default or who disable indexedDB. Because the uBO indexedDB
storage can’t be created. Worse, these people might think uBO works
because the default blocking lists are active, but not the added filters
beyond the default ones, and they might not realize that.

Please do not use indexedDB storage for uBO, rather use webext storage.
Otherwise this forces us to accept by default persistent tracking cookies,
html5 local storage cookies, and indexedDB evercookies. Those last ones
are especially nasty and stay forever even if firefox is set to clear
history on exit (another betrayal from Mozilla). Try it on jamendo.com 1 for
instance.

If I understood well, Mozilla made the anti-user and privacy hostile choice that tracking
cookies will be treated exactly like some forms of webextensions storage
(local storage and indexedDB storage), so that tracking cookies can’t be
blocked or cleared easily if webextensions choose to use these storages too. Please do not fall in their trap until they fix this (if they ever do).

HTTPS-everywhere fell in their trap, they now use local storage to store exceptions, and only just realized that it could be a problem for those irritating privacy conscious people who sometimes clear their html5 tracking cookies. ...