31–40 of 105 posts
Is it worth moving to this from 1Password? I mean I don't have any problems at all tho I use an old version (6 on Mac, 4 on Win), the permanent license version not this new subscription. I was thinking to use this with Dropbox, Chrome, and iOS client (MiniKeePass?)
Previous thread about KeepPassXC 2.2.0: https://news.ycombinator.com/item?id=14633576 I used KeePassXC for a period, but from these release notes, the UI/UX still isn't great. If you're on macOS, I recommend MacPass, which feels more native to the system, is compatible with existing KBDX databases and most-importantly, is also open-source: https://github.com/MacPass/MacPass
Given that I use multiple computers, and the extensions are synced, I want to use the same mechanism on all of them.
is it stable again? Last version was constantly crashing when modifying a new passwort entry again. This is something which is unacceptable for a password manager IMHO.
Is it worth to migrate from Keepass2 to this? Any interesting user experiences?
KeePass 2 seems to still be hosted on Sourceforge, and I'm not even sure where to get a copy of the latest (non-release) version of the source. The [Sourceforge repo][1] seems to be an outdated SVN repo which was last updated in 2009, and I don't see any description of how to contribute code to the project anywhere. As a result I'm not really sure how to gauge the level of activity on the project itself. Similarly, the website is ancient and doesn't seem to have kept up with the times; I seem to recall it was only recently that it even got HTTPS support.
In contrast, KeePassXC is hosted on GitHub, development is done out in the open, and it's trivial to see that in just the last year there were [dozens of individual contributors][2]. The website looks clean, is user-friendly with up-to-date documentation, and a [contribution guide][3] is plainly visible in the README on GitHub.
As a result, I feel a bit better about the long-term prospects of KeePassXC over KeePass 2.
[1]: https://sourceforge.net/p/keepass/code/HEAD/tree/
[2]: https://github.com/keepassxreboot/keepassxc/graphs/contribut...
[3]: https://github.com/keepassxreboot/keepassxc#contributing
Anybody have thoughts about where to store the encrypted database for backup? Would it be foolish to keep the database somewhere publicly accessible?
Anybody use this along with a non-tech significant other? How does it compare to commercial password managers in terms of usability?
Usability is too low, unapproachable for non techies. Even my somewhat technical spouse found it unusable after a few months. It could be better with good browser plugins, but then you have the same security tradeoffs as more polished services like Bitwarden or LastPass.
Not exactly. The database is handled with an independent program. With the new model, AFAIK, the browser extensions have no idea what records exist and can only query - and record matching is actually authenticated before plugin sees anything.
Anybody have thoughts about where to store the encrypted database for backup? Would it be foolish to keep the database somewhere publicly accessible?
Anybody have thoughts about where to store the encrypted database for backup? Would it be foolish to keep the database somewhere publicly accessible?
Since it got a lot of positive attention last time, here's a rough guide on getting started with password management, aimed at readers here who are not currently using a password manager: https://leclan.ch/password-managers/ TLDR: Download KeepassXC and start using it. :)