Leaderboard

thank you. if you do plan to continue push "Enpass-related news" straight into the app, please at least introduce another option in Enpass where users can opt out of such overhad. IMHO such content shouldn't exist in the precious memory-space of Enpass at all, use _any_ and _all_ other channels. thanks for hearing me out and keep up the good work

Thank you for the update.

Hi @sxc4567 I can understand the risks associated with this unfortunate situation. We use both mlock (to exclude memory from swap) and madvice (to exclude memory from dumps) for critical memory allocations. Please read this old reply to understand how much of the sensitive data is available in memory as plain text at a given time and how memory sanitization works in Enpass. We are continuously working to improve the security of Enpass and prioritized a memory sanitization review task to specifically handle this situation. Regards,

Hi @all, Thank you for your understanding. We apologize for any inconvenience caused by this matter. We were able to reproduce the problem on our end, due to which Dropbox authentication is frequently required. Our tech team is working on resolving this issue and a fix will be implemented shortly. Please bear with us while we get this resolved. Appreciate your patience and support in the interim. #SI-2785

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.

Hi @all We were able to reproduce the bug on our end, due to which this issue is occurring. Our dedicated development team is working on a patch right now, which will be released very soon. Enpass appreciates your patience in the meantime.

As far as i know enpass is perfect just without few bugs (if there are any) which enpass team fix but there is a feature which i miss in enpass. Which is PGP Features like few other password managers have. I think adding pgp to enpass will complete it's needs as one stop shop for most required security features. People like me use pgp daily and many people are getting aware of encryption using pgp so i think it is a great feature to have in a great password manager.

Hi @Fadi, Thank you for reaching out to us. I would like to share that I have duly noted your feedback and it has been forwarded to the concerned team for further consideration. #SI-2719