Mobile clients I haven’t tried yet, but looks like on iOS the choice comes down to these two:īoth are paid applications and are not cheap, but they do have a one-time purchase lifetime license option.Īndroid clients I haven’t looked at, as I don’t have Android devices. One thing I was worried about is whether KeePass has the functionality of storing 2FA/ TOTP codes, but it certainly does have that: It also seems to have better performance / more responsive ( and nicer) GUI. Unlike the reference client, which is written in C# and is for Windows only, KeePassXC is based on C++/Qt and works on Windows, Mac OS and Linux. Out of the desktop clients I liked the KeePassXC ( sources) the most. The full(?) list of clients on all platforms can be found here, under the “ Other downloads and links” section.
Many of those are available free of charge. Most of the compatible client application are proper native ( without Electron garbage) applications. a lot of native client applications on all the platforms, including mobile ones.database format (KDBX) and reference client application are open ( every release comes with the sources archive).offline database, which is just a file that you can host anywhere.So KeePass ended up being basically the only suitable candidate: But sadly neither of these two have proper native client applications. Then there are some solutions that do meet most of the requirements, and for example we could consider using Bitwarden or Passbolt. Here’re also some similar thoughts on the matter. And that was my first candidate, especially that they have some additional functionality for teams, but then they announced v8, which is destined to be a total shit: cloud-only, subscription-only, Electron-based - so that’s no longer an option. Personally I’ve been using 1Password, v6 and v7, while it’s still not based on Electron, with ability to have an offline vault and without subscription. proper native desktop/mobile client applications, and preferably more than one to choose from.no vendor-lock on a proprietary/closed format or software.
There are many password manager solutions available, but not all of them meet the following requirements: It’s not exactly meant for multi-user usage, but we came up with some sort of workaround. Having evaluated several options, we chose KeePass. Finally, we decided to stop this chaos and start using one common passwords database. For a long time in our team we’ve been storing logins, passwords, keys and other things like that in personal password managers or just plain-text files, spread around people’s machines, and no one had the full set.
0 kommentar(er)
