I am aware that this has been discussed at some length and that the official recommendation is to avoid adding extensions for maximum privacy. However, this post by a Mullvad contributor says there are certain conditions that may trigger an extension to alter a browser’s fingerprint.
The question is: does keepassxc and dark reader alter the fingerprint? From my very cursory tests with various fingerprint testing sites, it appears that they do not, but I would like more input from others. My goal here is to actually use Mullvad Browser as a daily driver rather than as something I sometimes use, and I consider these extensions very important for that.
If a site has realtime checks to see if its css is being modified then dark reader could be fingerprinted. There may be other ways to do it, but this is the most obvious one.
This functionality may be part of some fingerprinting libraries, but i don’t know that for sure.
It seems like this sort of fingerprinting may not be common. Maybe some highly secure sites check the ‘integrity’ of the page to make sure a user isnt being duped by some extension. It seems that sites like reddit, facebook, etc aren’t doing this though.
Yeah its rare, but it could be done. I personally wouldn’t depend on it not being common enough though. You could have it enabled on the sites you know for sure don’t check for it.