How does this compare to other popular solutions? Specifically, KeepassX / Keepass2 which are the most common solutions I've seen most Unix / Linux users employ. Can we objectively state which one is a better solution?
- There's no builtin GUI
- Each entry is its own file
- You control the storage format (meaning it's easy to store any kind of information, not just passwords)
- It relies on GPG, so you need to set that up first
pass -c (or --clip) does that for you.
Wrong, pass provides the -c flag which puts it in your clipboard and clears it after a timeout.
Of course one has to set it up, it's not an integrated solution. But GPG provides interesting features like storing encryption keys on hardware devices. Some devices like Yubikeys can have touch-to-use enabled. So each use of a secret requires a touch (after PIN but that's once a session). Perfect combination of convenience and security for me.
Do you mean this:
> YubiKey challenge-response support for strengthening your database encryption key
From https://keepassxc.org/blog/2017-06-26-2.2.0-released/
Then it's not clear for me how this works exactly.
In Keepass, there's a textarea associated with each password entry, which can be used to store extra data like security questions, etc.