Closed moenodedev closed 1 year ago
Just keep sensitive info in custom fields. (This also simplifies copy-pasting, by the way.)
Custom fields are first-class citizens of the kdbx
format which has been around more than 10 years. In fact, today it's harder to find an app that supports the old kdb
format. So the portability argument is very weak...
And if someone chooses to use kdb
for %reasons% — well, it does not support field visibility anyway…
You're right. Custom sensitive fields are easy and work in other apps. I was trying to avoid customizing the database too much.
It would be helpful to have a global option to hide Notes content until it's revealed.
If you're using multiple OSes and apps to access your KeePass database then you may only be using the basic fields for portability (Title, URL, Username, Password, Notes, OTPAuth). Notes is the only freeform field of those but if you have private info in it that content is displayed when viewing a login entry.