What do you mean with "use a key file and really lock down the database"?
I use Vaultwarden (which is an API-compatible Bitwarden server replacement, nice for self-hosting) and the "key file" is a sqlite database (so it is one single "key file"). It is "locked down" in the sense that even if a random user/attacker were to be able to download the file/db the contents would be meaningless anyway (that's the whole point of encryption :).
So I'd be interested in your ideas for (additional?) locking down of the database.
I use Vaultwarden (which is an API-compatible Bitwarden server replacement, nice for self-hosting) and the "key file" is a sqlite database (so it is one single "key file"). It is "locked down" in the sense that even if a random user/attacker were to be able to download the file/db the contents would be meaningless anyway (that's the whole point of encryption :).
So I'd be interested in your ideas for (additional?) locking down of the database.
Statistics: Posted by reinob — 2025-01-23 07:47