I dont agree with many things apple does at all, and I also think their password manager has flaws like revealing usernames without authentification.
It is pretty handy though, to have a file where the entries are stored unencrypted, and if the password manager detects an entry it prompts to decrypt exactly that field, maybe with a fingerprint.
KeepassDX needs to run in the background and be completely unlocked to even detect apps or password fields.
Do you know any existing app that can do this?
Use KeePassXC. Audited, code, open-source, highly customizable, zero cloud stuff.
Think its for mobile since they mentioned keepassdx
Yes I already use these. On Linux I use Kwallet, store my huge random Keepass password in there and unlock the Keepass database by fetching that password using a shortcut.
But still, then the password storage is open. Not as elegant as an on-demand password requester, especially on Android
Bitwarden if you want it in the cloud, Keepass if you want it on the device. I’d recommend PrivacyGuides.org’s recommendations this time. They are rather careful as to what they recommend, still doesn’t mean they always get it right.
What do you think about PrivacyTools.io? Are they on the same level as PrivacyGuides.org?
KeePassDX + Syncthing is the best solution.
Use that but its not about that topic. Its about storing unencrypted metadata (or usinh android Keystore for example) and having autofill work always even if the database is locked, and its quickly unlocked just for that entry
Kinda confused, you want a password manager that stores entries unencrypted but when you need them, the manager encrypts the entry and then prompts you for authetication to autofill the entry? That seems kinda dumb but if its just for convenience to not input your masterpassword everytime, keepassdx allows biometric unlocking. Think it’ll take as much time as what you described without potentially exposing any unencrypted entry info
Edit: Before someone jumps at my throat, security wise using biometrics is also kinda a no no but I understand not everyone has the same threat model so go for it if you want
If I understand it correctly, the passwords are stored encrypted, but not the additional data, like website-URLs and app-names. This way the password manager only needs to temporarily decrypt a specific password when it’s needed for auto-fill. In regards to the passwords that’s probably a bit safer than keeping all the data and the passwords unencrypted in memory. But the cost is that all the other data is stored unencrypted.
100%
