3 ms·

> Most of the preferences in this will actually reduce the target-able attack surface Can you point to anything specific that reduces the attack surface? When

> Most of the preferences in this will actually reduce the target-able attack surface Can you point to anything specific that reduces the attack surface? When looking at the "securefox" config, it does a bunch of strange things, like enabling embedded TikTok links (https://github.com/yokoffing/Betterfox/blob/443710b0738ebc8f45296a4f63c0bf362512d72f/Securefox.js#L60 https://github.com/yokoffing/Betterfox/blob/443710b0738ebc8f...) and disabling UITour (https://github.com/yokoffing/Betterfox/blob/443710b0738ebc8f45296a4f63c0bf362512d72f/Securefox.js#L158 https://github.com/yokoffing/Betterfox/blob/443710b0738ebc8f...) which Firefox uses to highlight menus and is only accessible by approved Mozilla domains (https://searchfox.org/mozilla-central/source/browser/app/permissions https://searchfox.org/mozilla-central/source/browser/app/per...). It's a very strange mix of configs.

autoexec 3y ago
> Can you point to anything specific that reduces the attack surface? I haven't had a chance to dig though those configs yet, but disabling things like service workers, webgl, normandy/experiments, pocket, and webrtc would be a good start at reducing attack surface
- throwaway290 3y ago
  All of that also makes you easier to fingerprint. How many people disable WebGL?
  - Beldin 3y ago
    Enabling WebGL makes you a lot more fingerprintable than having it disabled. See e.g. How gullible are web measurement tools? A case study analysing and strengthening OpenWPM’s reliability. B. Krumnow, H. Jonker and S. Karsch. In Proc. 18th International Conference on emerging Networking EXperiments and Technologies (CoNEXT’22). ACM, pp. 171–186, 2022. (Table 3).
yokoffing 3y ago
The section "Securefox" should probably be renamed "Privatefox", but labels are misleading. It's best to read the project files to understand the balance taken with security, privacy, and functionality. Let's make it simple: Want a mix of speed and privacy, while retaining functionality? Use Betterfox user.js. Want more privacy and security at the expense of site functionality? Use Arkenfox user.js. Want Tor prefs but without using its nodes/relays? Use Mullvad Browser. Want anonymity? Use Tor Browser.

autoexec 3y ago

> Can you point to anything specific that reduces the attack surface? I haven't had a chance to dig though those configs yet, but disabling things like service workers, webgl, normandy/experiments, pocket, and webrtc would be a good start at reducing attack surface

throwaway290 3y ago
All of that also makes you easier to fingerprint. How many people disable WebGL?
- Beldin 3y ago
  Enabling WebGL makes you a lot more fingerprintable than having it disabled. See e.g. How gullible are web measurement tools? A case study analysing and strengthening OpenWPM’s reliability. B. Krumnow, H. Jonker and S. Karsch. In Proc. 18th International Conference on emerging Networking EXperiments and Technologies (CoNEXT’22). ACM, pp. 171–186, 2022. (Table 3).

yokoffing 3y ago

The section "Securefox" should probably be renamed "Privatefox", but labels are misleading. It's best to read the project files to understand the balance taken with security, privacy, and functionality. Let's make it simple: Want a mix of speed and privacy, while retaining functionality? Use Betterfox user.js. Want more privacy and security at the expense of site functionality? Use Arkenfox user.js. Want Tor prefs but without using its nodes/relays? Use Mullvad Browser. Want anonymity? Use Tor Browser.