Leaderboard

Hello, I upgraded to 6.0 today and was really looking forward to the vault feature in the hope that one vault would be shared while the other would not. My setup consists of 3 windows devices and 2 android devices (each with their own PRO licence). I managed to generate the new vault but when I come to tell it to sync to the same google drive location I get an error telling me that this is not possible. In my opinion the name of the first vault was system generated while 2nd vault onward require a name. Can't this name be used to generate a unique file name? Thanks and Regards,

Hello, I think being able to sync multiple vaults with one cloud would be a big benefit! I love the idea of multiple vaults in Enpass, but having to use different clouds is a bit of a pain - I would like to have them all in one place. Could you please add support of multiple vaults for the same cloud? Thanks!

Hey @GeoLuz, To know more about Enpass extension security, please visit: https://www.enpass.io/docs/security-whitepaper-enpass/browser_extensions.html#browser-extensions Hope this answer your question.

It appears that you (GeoLuz and tox1c90) are in the "exception" rather than "rule" category for Enpass v6. It also appears you are primarily Edge and smartphone users of Enpass, both of which are incredibly castrated environments compared to the full-function desktop experience we have with Enpass v5 in full-function browsers like Firefox, Safari, Chrome on a desktop. As for compatibility issues, if version 5 ran reliably and flawlessly, then as soon as v6 installed by Enpass's auto update and completely blew up (extension can't reliably connect with the application, can't find the data store, and when it does hook up, can't auto-invoke the credentials for the log-in page you have invoked - the most basic reliable function of version 5) then the onus is on Sinew Software, NOT users, to fix the problems. The sheer volume of problems indicate this was an update to please Enpass, and the fancy Windows messaging version (so Microsoft can insert itself into your machine security situation and try to force you into OneDrive client-hood). There was apparently no or little attention paid to impacts of design and coding changes to the "Traditional" version and interfaces with non-Microsoft extensions. The fact that Sinew Software remains silent, provides no updates to address all these issues and no help to those they apparently ignored in the beta test / release cycle indicates that their roadmap is a Microsoft / Edge / Window phone / OneDrive centered plan so that users of non-Microsoft browsers can just fall to the wayside, live with the problems or find other products that actually work with non-Microsoft browsers and cloud services. The Sinew Software silence, their lack of effort to address these issues is the coward's way out - they should just tell Firefox, non-MS cloud service users etc. that they will no longer support these browsers / services and make a clean break with those users who have been forced back to version 5 with all the SERIOUS functionality and reliability downgrades the auto-update to version 6 inflicted upon them. But I'm happy that those who are enamored of Edge and OneDrive, Microsoft Store app versions etc. have a product that works for them. It is still no help for the rest of us who swallowed the Sinew Software "good will" based on experience through version 5 on other browsers.

This architecture of one vault per cloud service and the insistence on using non shareable folders fails to take account of how actual users work in the real world and offloads complexity unnecessarily into the user instead of working out the appropriate application architecture to support actual use cases. Multiple vaults as implemented is not workable in the real world. As a user I refuse to setup another Dropbox account in order to share vaults with my family because Enpass has setup a deficient application architecture.

Hi @Klaas Vaak, By default Enpass stores its data under /home/<your-username>/Documents/Enpass folder. Thanks.

Hi, @Vinod Kumar Thanks for the reply. Would it not be possible (at least for Google Drive); to simply let Google's file permissions handle it. e.g. Sharing a vault with my client I would need to first share the folder (Via Google Drive), then they can get their own OAuth token, and point the vault to the in their own drive account. (This would also mean that if I decided later to revoke access I could just remove their permissions on Google Drive). With a little more code, it could be that Enpass verifies permission to the folder via the Drive API and gives the request access button if they don't. Please, Please, Please reconsider this. I love the idea of Vaults, but simply can't use them as they are now.