![]() ![]() 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. Just my two cents.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. ![]() Please document this as it should be, otherwise it feels like the feature was just half baked and it does not even work. Adding a feature and then saying to users "We don't know how this works you are on your own is a bad business practice when you are charging for the software". Part of offering a commercial software and expect people to pay it is properly developing the tutorials, documentation and supporting the functions of the product. We would go with open source and free software is we want no documentation and support. How are customers going to know what the software does or reacts to different configurations with external software if there none documentation about it? ![]() I had a similar question about KeePass and your team took a year to reply because there was something not documented. If it's not a good idea why did the developers added the feature? I don't think anyone expects JetBrains to explain how PGP works, but to document how the IDE works regarding keys and PGP. ![]() I agree with Ragdata, there is no documentation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |