Leaderboard

@johnq please try re-connecting the Dropbox sync one more time. I have similar issue which gets fixed after re-connecting. Thanks!

I deinstall Enpass on my Windows 11 System and after reinstalling from the Microsoft Store a can't get any connection to my Web Dav. The old one to my standard vault (which worked before the deinstall - in my opinion because it was already there) and even a new connection didn't work. This is really annoying. @Abhishek Dewan - I will sent you a DM EDIT: After Reinstalling the App again now it is working. @Abhishek Dewan: Is disable the Demo-Account cause it's working now :-)

I think you do, if you set "Lock on leave", you want to authenticate each time Enpass goes to foreground, that's the whole point. Majority of Android users use biometrics, which makes unlocking as fast as unlocking the screen. If you don't have or want to use biometrics, you can change you password making sure to use a keyfile and a shorter password

No more issues with Dropbox in beta 6.8.2 for Android neither

Hi, all I builded flatpak package for enpass. I have a question: can I share it on flathub (https://flathub.org)? I want to get permission for this from the project team.

At this point Enpass works on "most" distributions, but not on all of them. Also, there is the need to add a repository and then install the application. My request is to make Enpass available as a AppImage, snap or flatpak. This way the support for Linux can be improved! I would suggest to use AppImage or Flatpak, since snap = canonical controlled.

As i have been using enpass for past several months i even got to know about enpass key file to enhance vault security but there are still few concerns which i am about to share. 1: for security new users do not know about enpass key and once a new user have created primary vault then it is almost not possible for them to move to another vault and keep primary vault without enpass key. There is no option to set or change default primary vault if i want to. 2: Even if you have created primary vault with enpass key it can be hacked very easily. Enpass Database + keyfile is located on same system once a hacker got into your pc using RAT which is very common scenario they can access your all files in drive and using key logger they can capture your password for enpass. So when a hacker have access to a pc having enpass keyfile does not make it secure. I am a security researcher and i know what i am talking about. Now a days malware have became so intelligent they can be asked to find specific file on that computer or even on that network and once they find name of extension matching file it can be uploaded to hacker's server. having 2FA on Authy or Google Authenticator or which ever you use is much more reliable way to add an extra layer of security to your enpass vault. Why don't we put a 2FA by default for primary vault? Even if it is protected by key file on new device vault must ask for 2FA code? It can be implemented and user gets to choose if they want keyfile and 2FA both activated or only key file or only 2FA. I have tested the scenario (2) explained above using my personal computers and i was able to access it very easily. It is my humble request to add this 2FA including keyfile to make enpass more secure and a single keyfile and a password is not enough to secure it. even if we keep keyfile on a USB drive our vault needs it and when we will connect our USB to that pc for vault unlocking it can be accessed by hackers like all other normal drives. Also please add feature to change primary vault if someone creates a new vault with keyfile or how ever there must be an option to change primary vault. I hope i am not missing anything and was able to explain it clearly but if i am missing something please do let me know.

Hi @flyingbirds The backup file created by going to Enpass Menu -> File -> Backup is encrypted. Exporting a file, which can be done by going to the Enpass Menu -> File -> Export, however, does not encrypt the data. Upon creating a new vault/on the app's welcome screen, you can choose Restore from Backup File option to restore the backup file. Regarding saving the manual backup file on the cloud storage of the user's choice, I have forwarded your comments as feedback to the dedicated team so they may check the feasibility of this feature and look into implementing it for future Enpass versions. Thanks for your continued support and patience in the meantime. SI-2867

Hello, Please add the option to add bookmarks to your product. An old post mentions there are cross browser plugins for this. Unfortunately the programs i have looked at so far all require online accounts...and using your product for the offline database feature, defeats that point. If you believe there are some good cross browser bookmark products, please give some examples that I can install while completely offline, and never get synced with a server. I am trying to move from Roboform to your product. Having Bookmarks all in the same product is one less thing to install....and makes things very convenient when switching browsers because a website isn't behaving in chrome. Plus when i eventually sync to a USB drive, while on the road, it will be nice to have all my bookmarks come along. I can create a tag or folder called bookmarks as a work around....but it is very clumsy. thanks

First make sure its not a problem from your side. Here are something you can try:- Restart Enpass restart your computer make sure caps lock is not ON make sure keyboard is set to the language of password (if password in english, keyboard input has to be in english if you are bilingual) On your device you will find backups of Enpass vault, download enpass on your phone or other computer and try to unlock that vault using your password from there. As a protective measurement, I have opted to use 2 password managers just in case one fails me as EnPass has failed you. I am currently using Bitwarden as backup and often export from Enpass to Bitwarden to keep passwords up to date. Bitwarden is free.

Hi, got the store Update: And WebDaV is back fully working! So much thank you ;)

Cool! Thank you for informing me

Never mind.. I restarted the enpass app en both categories and tags appeared..

Thank you. That point hadn't occurred to me.

Installed, thank you very much

Hi guys, exactly the same problem here with version 6.8.1 (1060) from Microsoft store. I have also downloaded the latest version directly from your website, but unfortunately the same issue occurs. Please fix asap. Thanks a lot in advance.

Hi @Manish Chokwal, I sent the requested files to support except the log files because there aren't any created by the Enpass Manager. If we get a solution for this problem I will post it here.

Hi @Dani It is not required to remove the Enpass ver 6.8.0 to install 6.8.1. In the case of mobile devices, you can update the app from the PlayStore/ AppStore. On Desktop devices, you can visit the dedicated Store (For the Enpass Store version) or on your Enpass app, go to Hamburger sign -> help -> Check for updates. Otherwise, please let me know the device on which you are trying to update Enpass, and I'll assist you with the appropriate steps.

Fixed in 6.8.2.

Thanks for looking into this, Abhishek, I appreciate it So to answer your questions: Just one vault. My vault has 21 files with attachments, and I counted about 64 individual attachments. In total, I have 416 items in that vault. I'm using Google to sync.

Thanks @Ivarson. You are 100% right here. @sxc4567PIN locking is a convenience feature and only restricts app access. It does not close the underlaying SQLCipher database handle and an unencrypted database page may still be there in process memory. However, there is an additional level of encryption for the stored passwords with a per item obfuscation key to prevent direct visibility in memory for this case. Though, an attacker with advanced skills can still find the obfuscation keys and decrypt it. Locking with master password is the safest option for Linux as it will close all underlying resources too. Cheers:)

yes, we need this!

This really is the core of the issue for me. Running through Rosetta hasn't had an impact on performance, and I haven't noticed a hit to battery. In a vacuum, this wouldn't be a problem, I knew what I signed up for when I got a first generation product. But this is a password manager. It's one of the few applications where fast, timely updates are very important. If there's an exploit in the future, should we just expect our data to be exposed for 2+ years while you guys wrangle your code gremlins? I've worked with Qt before, and quite frankly, I would be mortified if it took me 10 months (since Qt 6.2 was released) to integrate upstream changes. I can't imagine looking my boss in the eye and telling him that the reason something this fundamental is taking so long is because of some deprecations. Qt is a UI framework, it really shouldn't be taking this long to handle a few deprecations. I don't buy the excuse that it's truly taking this long to update your UI, and I don't even want to imagine what hell-spawn spaghetti code you're working with where some deprecations in a UI framework requires a total rework of your codebase.

I totally agree with @dahliamma and @pitchblack It is totally unaceptable that two years later, in most cases, this is the only not native application that we are running. You say in the recent release: I CAN'T beleive that your developers have released a BIG update without native support. The password manager perhaps is the most importan app in a computer (at least in my case). Is this a reliable company to trust my most precious data? I'm not sure.

I too would like to have a flatpack version of enpass. That would be very handy, since the SteamDeck does support flatpack packages. So enpass has the chance to be one of the first (commercial) Password Managers on a gaming console.

Sorry but your newest Enpass version 6.8.0 for MacOS & iOS is a complete disaster. WebDAV synchronization is not available anymore. I wasted a lot of time before I recognized that your app is responsible for that issue. I could go back to version 6.7.4 on MacOS (whre it works) but no chance in iOS. Do you not test your software before releasing? When do you plan a patch for it?

While we understand your concern @dahliamma, Enpass would like to assure all that our developers are working on it and the launch of Enpass native macOS app is getting delayed due to extensive migration(as mentioned above). However, we would again confirm that Enpass will be available for macOS natively very shortly. Looking forward to your support and patience.