Completely disabling WebRTC now possible only with third-party extensions like "WebRTC Control". Navigate to Settings → Advanced → Privacy and Security → WebRTC IP Handling Policy and choose Disable Non-Proxied UDP. Really great protocol and lifesaver for many video and audio chat applications, just with one small issue: IP address and machine ID leak is very possible. How to disable: $ brave -js-flags=-jitless. Available in Settings → Net Tab Page → Blank page.ĭisabling Just-In-Time JS compilation to native code costs some browser performance and heavily increases security at the same moment, 'cause JIT-related security issues are very popular. Wallpapers and widgets are cool, but can leave some traces hitting external APIs. Cache in the RAM will also increase browser performance. Make sure to check read access rights, cause browser cache shouldn't be available to read for all users. With the -disk-cache-dir flag, the cache location can be changes to a temporal directory: $ brave -disk-cache-dir="$XDG_RUNTIME_DIR/chromium-cache" The cache is critical for security and can be cleaned from time to time. Heavily recommends enabling it all - websites will be cleaner and less info sent to Facebook or Twitter is always a positive moment! This blocking not social media like, but their widgets, buttons, comments, login widgets. Subscription to a regional filter list will potentially save you a lot of time. Local content filtering is also very useful: go wipe a button or a gigantic privacy policy widget you don't like. Why it's so important? Every widget/button/script can leave a cookie and then when you'll open another website they will compare the cookie and Game-Set-Match: tracking is set now. This should be enabled by default, but worth to check again. Enable "Auto-redirect AMP" to connect publisher websites without Google front, "Block Trackers > Aggressive", update connections to HTTPS and finally, very important - block cross-site (third-party) cookies. There's good fingerprinting test made by EFF, heavily recommend. Canvas fingerprint can be disabled with -disable-reading-from-canvas flag on Chrome-based browsers. There's a warning about breaking sites, but we recommend Strict anyway 'cause of good experience. Navigate to Shields → Block fingerprinting and choose Strict. Most of the options below will work for Chrome, Edge and Chromium-based browsers.ĭeanonymization using WebGL object rendering or even background audio playback.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |