zyghom

pricing actually is on the front page so ... ;-) but the rest I must agree - it used to be better here ;-(

yes, and only because developers made the Enpass.. you know what they did with 6.x version and why all this discussions started you should have been here before 6.x - that was really TECHNICAL forum with state of the art answers from devs now... look around

I am afraid I am in the same situation so welcome to the club someone already said in this forum: if they (developers) did NOT do anything with 5.x it would be MUCH better than what happened to and with version 6.x eh...

actually even 3 times if you have - like me - iPad, android phone and macOS

@OLLI_S I agree with you in 99% maybe even in 99.9%. ;-)

mobile version is paid separately ;-(

+1

on first use you should use master password by design - otherwise it is a security issue

perfect but let me know please if you use Enpass offline only then? if so how do you sync between phone and desktop? because if you say you use any cloud solution there is no difference (much at least) between fully encrypted vault from Bitwarden on their server and iCloud/OneDrive/Google/Dropbox (you name it) on top of that: 1- Bitwarden just got fully audited by 3rd party company and report is available (nothing for Enpass even scheduled) 2- Bitwarden is fully open source (Enpass is proprietary - you have NO IDEA how they implement anything) 3- you CAN implement your own solution (cloud service) for Bitwarden (that is what I am exploring now) There is NOTHING fully secure - it is only a matter of resources to get things "done" (read: deciphered)

Bitwarden imports json

"Bitwarden: it's really free, not a fake "free trial free"" - I believe they summed up the Enpass correctly ;-)

there is a whole debate about it - pity the developers are not even participating in it on top of this: if you want to revert to 5.x you need to keep the old file - once you upgrade vault to 6.0 you will not be able to return

Keepass for win and its derivates for Android, iOS and MacOS

I did this for iOS and MacOS

just take the file with vault and put WHEREVER i.e. desktop or so uninstall/install Enpass and during first run use "open the vault" (or so - I don't remember what is says exactly) and point to the file you stored Then it shall accept the password it worked on one of my comps - before that it was just not accepting the password

I had the same issue with one of my installation. The solution for me was: use the file from last backup or vault and use it as NEW vault - not trying to use the old installation. Even if this means you need to uninstall the old one and install fresh and then, instead of upgrade just open the old file.

you can copy paste using Command + C and Command + V old fashioned style ;-)

once you opened vault from 5.x in 6.x and saved you cannot open it back in 5.x so only if you kept 5.0 vault somewhere you can come back and this is not only very unfortunate but not described anywhere...

it does but I am left with version 6.0 only now so 5.6 cannot open it

most of the features you are working now are cosmetic changes (I believe) - not new functionality related to the security so audit could be done on major releases yes, it is costly but yes, it buys the Customers

Hi there, seeing that 6.0 is not what I was expecting (after few weeks of using it on Mac, iOS and Android) I would like to return to the versions I paid: 5.6 (both Android and iOS) unfortunately my database has been upgraded to 6.0 how can I return to 5.6? export from 6.0 to .json is not recognisable by version 5.6 please advice

6 months testing and such issues... eh

same for notes field - not possible to scroll it even (MacOS)

+1

that is ok and what I like in new Enpass is: forced use of master password from time to time so anyway, if finger print is not working you should use your master password forgetting it must mean: zero otherwise... I already said it