Nothing worthwhile is not without risk. The only true way to combat this is to carry around your passwords with you at all times written in a notebook.
There a several things the Keepass desktop client supports for the extra paranoid:
- You can disable remembering the locations of your password files
- Your password file can be called anything, and located anywhere.
In particular, I don't use a .kdbx extension, as you can just as easily store it in a file named 'taxaudit2015.xlsx' or 'reallybadsong.mp3'.
- As I noted above, use a Key File as well as a master password, and if you sync through a cloud service, keep the key file in an unsynced location - then just manually copy the key file to any devices you need it on.
- Use the Portable Keepass version, and store the app in an obscure location or on a USB key.
- You can use a Yubikey (haven't tried, but they're an external hardware token)
I do steps 1-3 of these, and while it's a bit of security-by-obscurity, when combined with step 4 it leaves your device itself with no obvious signs that you use Keepass at all.
Of course malware that watches your activities could technically gather all that info, and a hack that totally busted the protocol would still have the protection of your database being called reallybadsong.mp3.
I think they're solid protections against large scale attacks which would target common configs.
Extra : Use Keepass for 'Estate Knowledge Escrow'
My sister-in-law died several years back, and we had a beast of a time finding everything we had to wrap up for her.
Enlightened by this, the Keepass file that my wife and I share also contains things like insurance policy details, and utility account numbers, as well as passwords.
The idea is that if we both keel over suddenly, our lawyer and executor have access to a list of everything they need to sort out.
For safety we gave separate parts to our Lawyer, Executor and a (technically adept) friend:
- Lawyer
a/ Copy of initial database, and means to access live copy
b/ Password
- Executor
a/ Copy of Key File
b/ Password
- Friend
a/ Copy of initial database, and means to access live copy
b/ Copy of Key File
The theory being that any two of the parties can get to the info, but none can one their own.
Hasn't been tested -and if there is cause to, I won't be here to post the outcome!