KeePassXC 2.4.3
41–50 of 67 posts
Re: KeePassXC 2.4.3
#42Re: KeePassXC 2.4.3
#43Earlier quoted context omitted.
KeePass is the original project. It is an open source dotnet application. The source code, as of the last time I checked, is released as a tar/zip with the binaries only. KeePassX is an open source c++ application. It was one of the cross platform applications to manage KeePass databases. It has not been under very active development for a while. KeePassXC is a fork of KeePassX which is under active developement. The…
KeePassXC is fantastic, I especially like the good Yubikey integration. The one small feature I miss from the original KeePass was the password templates. I like all my passwords to follow a grouped pattern so its easier to type into a phone or something while still being strong.
Re: KeePassXC 2.4.3
#44Earlier quoted context omitted.
KeePass is the original project. It is an open source dotnet application. The source code, as of the last time I checked, is released as a tar/zip with the binaries only. KeePassX is an open source c++ application. It was one of the cross platform applications to manage KeePass databases. It has not been under very active development for a while. KeePassXC is a fork of KeePassX which is under active developement. The…
Is KeePassXC also audited? The main KeePass has had multiple security audits, also thanks to the EU who funded it one time. Seems relevant for a password manager.
Re: KeePassXC 2.4.3
#45KeePassXC still lacks in-memory protection, so I stay with KeePass, with all its .NET troubles.
In fact, KeePassXC has shown to have better memory protection than KeePass: https://keepassxc.org/blog/2019-02-21-memory-security/ (note the article is from February, some things have changed since then, see below). The only thing we do not have at the moment is in-memory encryption. We do, however implement the following security measures on all platforms:
- prevent swapping of master key hashes (using gcry_malloc_secure)
- prevent non-root / admin access to our process memory (KeePass does NOT have this)
- overwrite all dynamically allocated memory with zeros on free
- disable any kind of coredump or crash reporting
A patch for in-memory encryption is being worked on, but needs further testing before it can be merged: https://github.com/keepassxreboot/keepassxc/pull/3055
Please note that this still cannot fully prevent swapping out of secrets. As soon as things are to be displayed somewhere in the GUI, they are basically out of our hands. We also cannot fully protect everything while the database is being loaded or written. However, the same applies to KeePass. There is just too much going on with memory management on modern operating systems.
Re: KeePassXC 2.4.3
#46KeePassXC still lacks in-memory protection, so I stay with KeePass, with all its .NET troubles.
(Full disclosure: I contribute to KeePassXC) In fact, KeePassXC has shown to have better memory protection than KeePass: https://keepassxc.org/blog/2019-02-21-memory-security/ (note the article is from February, some things have changed since then, see below). The only thing we do not have at the moment is in-memory encryption. We do, however implement the following security measures on all platforms: - prevent swapp…
Re: KeePassXC 2.4.3
#47Re: KeePassXC 2.4.3
#48Earlier quoted context omitted.
KeePassXC is fantastic, I especially like the good Yubikey integration. The one small feature I miss from the original KeePass was the password templates. I like all my passwords to follow a grouped pattern so its easier to type into a phone or something while still being strong.
Keepass has templates for password generators. You can create custom templates as well. I've been using it since 2008 without any issue.
Re: KeePassXC 2.4.3
#49I was only aware of Keepass itself. What are the differences between KeypassXC, KeepassX and Keepass?