I keep the db + image file in a selfhosted (gitea) private repo. The repo contains 100s of files and I named the keepass files very general to hide in the open if my server is hacked.
Hmmm... I haven't taken a look at what the raw DB file looks like but I imagine it wouldn't be too hard to differentiate from the other files if looking at the bytes on disk. Food for thought...
Yes its possible, but needs finding out. There is also another file among the 100s that needs to be used with a strong password tough. All these layers make me feel it's safe enough
For my own ultra-secure (offline) storage, I use a strong password for a KeepassX DB stored on a LUKS-encrypted USB drive that's only plugged in when needed. Layers are the way to go ;)
Comments
I keep the db + image file in a selfhosted (gitea) private repo. The repo contains 100s of files and I named the keepass files very general to hide in the open if my server is hacked.
Hmmm... I haven't taken a look at what the raw DB file looks like but I imagine it wouldn't be too hard to differentiate from the other files if looking at the bytes on disk. Food for thought...
Yes its possible, but needs finding out. There is also another file among the 100s that needs to be used with a strong password tough. All these layers make me feel it's safe enough
For my own ultra-secure (offline) storage, I use a strong password for a KeepassX DB stored on a LUKS-encrypted USB drive that's only plugged in when needed. Layers are the way to go ;)
Right on :)
What do you mean by db + image file?
Strike image. I just happen to use an image. KeePass db can be locked using a password AND a file