AnakinCaesar

So you chose to completly ignore my advise on Reddit?

You just have to enter your email address again and there you'll recieve a code to authenticate you.

Seems like you dont understand the silent agreement in cyber security and how things are handled. After a disclosure in private (April) Enpass rolled out a temporary fix in May. While working on a permanent solution, the world was notified, that this problem exists (August) and then Enpass rolled out a permanent fix just 4 days later (some popular managers still have no fix [1Password, LastPass, KeePass, iCloud]...) This is still common and in my eyes quite a rapid reaction. Also, change logs indicated the fix in May already. There is a common ground that has to be found between telling users and risking "bad guys" actively acting on the notification and not telling the users and increasing the change of the vunerability not gaining a lot of attention. It's a fine line.

Maybe you should keep reading the Data Security forum posts here: https://discussion.enpass.io/index.php?/topic/31873-update-on-dom-based-extension-clickjacking-vulnerability-in-enpass-browser-extension-fixed/

Do you store your vault in a OneDrive location? If so, the token might be expired and needed a re-authentification.

I guess one way to do this kind of easy would be exporting your entire vault and then searching in the created file for the affected entries. Then you could either clear all current entries in your vault and import the corrected export file. Or manually open all entries (after finding them in the exported file) and correct them. Not a nice way, but from my pov and knowledge the fastest/easiest.

Could you not check for the last used / accessed file and determine from this? Otherwise I suggest, you keep the vault.enpassdbsync, as this is on my site the frequent used file. Which files else do you have?

Please provide more information, including Enpass version, macOS version, used browser and link to non-functioning loginform, otherwise helping will be quite difficult for the Enpass team.

This is the normal startup for Enpass installed through Windows Store. Some users have made the same remarks as you, but to my knowledge there is no solution for it.

I can totally understand your frustration but have no clue on how Enpass verifies/signs a browser. Hopefully they’ll add it soon and keep it supported.

You could try and deactivate the browser signature check in the Enpass app

Why should I say something along the lines of if I'm no way affiliated with Enpass. All I'm doing is pointing into the right direction. Also I said the users solved their issue of not syncing, the underlying issue of course is not fixed by it. And if you don't care about the cause, then why don't appreciate a fix for your current situation?

Try this for now: https://discussion.enpass.io/index.php?/topic/31671-icloud-sync-is-broken/#findComment-91741

Maybe you should read about the changes between Mainfest v2 and v3 and what it means for every chromium based browser. Then you should read, how many browsers are based off of chromium. Maybe then you will understand, that developers sometimes need time to adjust to those dramatic extension changes.

Nobody ever said, its a solution. Get your head straight. You want it to work in the short term, use this fix, if you're not satisfied wait for the chromium fix. Whatever floats your boat. It was just a suggestion to get you up and running again, but even that seems too much energy spend for someone like you.