commit 299489c701cb9da341da176c9c4aa87bb80861a9
parent 50a578c32ab1efd73361545cd5c284805f7b43a5
Author: Thorin-Oakenpants <Thorin-Oakenpants@users.noreply.github.com>
Date: Tue, 28 Aug 2018 08:27:45 +0000
1000s: cache description/info, closes #436
Diffstat:
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/user.js b/user.js
@@ -609,7 +609,17 @@ user_pref("security.insecure_field_warning.contextual.enabled", true);
* [1] https://bugzilla.mozilla.org/1357835 ***/
user_pref("network.auth.subresource-img-cross-origin-http-auth-allow", false);
-/*** 1000: CACHE [SETUP] ***/
+/*** 1000: CACHE [SETUP]
+ ETAG [1] and other [2] cache tracking/fingerprinting techniques can be averted by
+ disabling *BOTH* disk (1001) and memory (1003) cache. ETAGs can also be neutralized
+ by modifying response headers [3]. Another solution is to use a hardened configuration
+ with Temporary Containers [4]. Alternatively, you can *LIMIT* exposure by clearing
+ cache on close (2803). or on a regular basis manually or with an extension.
+ [1] https://en.wikipedia.org/wiki/HTTP_ETag#Tracking_using_ETags
+ [2] https://robertheaton.com/2014/01/20/cookieless-user-tracking-for-douchebags/
+ [3] https://github.com/ghacksuserjs/ghacks-user.js/wiki/4.2.4-Header-Editor
+ [4] https://medium.com/@stoically/enhance-your-privacy-in-firefox-with-temporary-containers-33925cd6cd21
+***/
user_pref("_user.js.parrot", "1000 syntax error: the parrot's gone to meet 'is maker!");
/** CACHE ***/
/* 1001: disable disk cache ***/
