We’re seeing an increasing amount of users reporting incompatibility of Enpass Extension with Brave Browser. We’ve identified the problem and isolated it to Brave Browser’s shields blocking all localhost network requests. Upon disabling the shields, the Enpass extension resumes the usual functioning.
Enpass uses localhost connection to establish communication between extension & native app and this functionality is essential to the core functioning of Enpass. The localhost connection is purely used for native app communication and isn’t related to any tracking or fingerprinting activities(which we don’t do anyway). This method of process communication is used very widely by numerous extensions and is supported by all major browsers. To resolve this problem, Brave browser could, in theory, keep blocking websites that are trying to fingerprint users and yet allow extensions to communicate on localhost. Or at the very least, there should be an option/permission to whitelist certain extensions so that Enpass users don’t face this problem in the future.
Some users have reported earlier on the same forum-