10

Related to this >:y

Featuring:
Jerky Hooves / Ask Joen / Cauldroneer NSFW / Firefox / Internet Exp / Honey Dip NSFW / Meanie Belle / A Giraffe / Safari / Every Chrome Blog / Frigid / Fluffy / you saw nothing / Wiggles / Raikissu / Maple / Bag is love Bag is life

Firefox: Privacy Related "about:config" Tweaks

Preparation:

  1. Enter “about:config” in the firefox address bar and press enter.
  2. Press the button “I’ll be careful, I promise!”
  3. Follow the instructions below…

Getting started:

  • Disable referrer headers.
  • Disable referrer headers between https websites.
  • This is Mozilla’s new built in tracking protection.
  • Disables geolocation.
  • Disable Google Safe Browsing and phishing protection. Security risk, but privacy improvement.
  • Disable Google Safe Browsing malware checks. Security risk, but privacy improvement.
  • Disable that websites can get notifications if you copy, paste, or cut something from a web page, and it lets them know which part of the page had been selected.
  • Disables website control over rightclick context menu.
  • Disables firefox logging geolocation requests.
  • Disables acceptance of session cookies.
  • Disable cookies
  • 0 = accept all cookies by default
  • 1 = only accept from the originating site (block third party cookies)
  • 2 = block all cookies by default
  • cookies are deleted at the end of the session
  • 0 = Accept cookies normally
  • 1 = Prompt for each cookie
  • 2 = Accept for current session only
  • 3 = Accept for N days
  • Number of cached DNS entries. Lower number = More requests but less data stored.
  • Time DNS entries are cached in seconds.
  • Disables recording of visited websites.
  • Disables saving of formdata.
  • Disables caching on hardrive.
  • Disables caching for ssl connections.
  • Disables caching in memory.
  • Disables offline cache.
  • The attribute would be useful for letting websites track visitors’ clicks.
  • If your OS or ISP does not support IPv6, there is no reason to have this preference set to false.
  • To disable DNS prefetching you will need to add network.dns.disablePrefetch as a new boolean preference and set the value to true.
  • Link prefetching is when a webpage hints to the browser that certain pages are likely to be visited, so the browser downloads them immediately so they can be displayed immediately when the user requests it. This preference controls whether link prefetching is enabled.
  • WebSockets is a technology that makes it possible to open an interactive communication session between the user’s browser and a server.
  • WebGL is a potential security risk. Source

Source and thanks to reddit users aboutconfig_tips and FreddyFredG

Thank you everyone for showing this blog so much love! Its amazing how fast we got to 300. You guys are great, really, a lot of fun questions and a lot of fun streams. I hope I can do another one of these soon

People in update (In no order):
http://inofoxywolf.tumblr.com/

http://heartsmodblog.tumblr.com/

http://ask-leah-pony.tumblr.com/

http://ask-cloudkicker.tumblr.com/

http://askopera–pony.tumblr.com/

http://askfillyrarity.tumblr.com/

http://misty-field.tumblr.com/

http://spartan309.tumblr.com/

youtube

Happy Leif Ericson Day! Just to show how silly we are, I remixed the song “Spazzmatica Polka” by Kevin McLeod, and then my friends and I all flew to the moon to play it! 

((Enjoy guys, I spent the pest 2 weeks working on the song and animation! Also midterms are over so I’ll soon resume your regularly scheduled Chrome. Oh, and my birthday is in a week. April 8th. Same as last year.))

Is your IP address leaking?

WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN.

While software like NoScript prevents this, it’s probably a good idea to block this protocol directly as well, just to be safe.

Test your Browser now

How to disable WebRTC in Firefox?

In short: Set “media.peerconnection.enabled” to “false” in “about:config”.

Explained:

  1. Enter “about:config” in the firefox address bar and press enter.
  2. Press the button “I’ll be careful, I promise!”
  3. Search for “media.peerconnection.enabled”
  4. Double click the entry, the column “Value” should now be “false”
  5. Done. Do the WebRTC leak test again.

If you want to make sure every single WebRTC related setting is really disabled change these settings:

  1. media.peerconnection.turn.disable = true
  2. media.peerconnection.use_document_iceservers = false
  3. media.peerconnection.video.enabled = false
  4. media.peerconnection.identity.timeout = 1

Now you can be 100% sure WebRTC is disabled.

Test your Browser again

How to fix the WebRTC Leak in Google Chrome?

There is no known working solution, only a plugin that is easily circumvented. 

.