Leaderboard

Hi @Unsay, Thanks for your suggestion and pretty detailed one. The solution you proposed is very feasible provided we have enough time to do this major refactor. We are planning a major UI/database/sync engine redesign of Enpass next year that will implement many new features that are not feasible with current architecture. I think that will be suitable time for considering your suggestion.

Hi ! I'm an user of mac os x (with bootcamp windows) I have an iPad but I sell my iPhone and i use an Android phone for my password I use Keychain Apple but it don't compatible with my Android :-( I want to use Enpass because I prefer to buy it one time ;-) I don't want an subscription all the time. I want to import my Keychain ? I do export with a command terminal my keychain in format txt I can't to import in Enpass !? I convert to Csv but again I can't to import too !!! What the method to import my Keychain Apple ? Thank's ps : sorry for my langage I'm French

Hi, Ok, This request has been raised many times by our users. It will be discussed in next meeting positively.

Lack of multiple vaults support would be the one thing to hold me back from adopting enpass. I have used eWallet for 10+ years and am considering enpass primarily because of Linux support and because eW doesn't seem to see much innovation in recent years (eg: their iOS integration is still subpar). I tried 1password but it failed at Linux support and also proper multi-vault support. I'd suggest keeping it simple; separate vaults which can (easily - 1-click) be selected at startup, stored in separate files/databases. For users who don't care about multiple vaults, this shouldn't intrude their workflow. I think eWallet's implementation of that feature is "just right"...