Repository navigation
Help me understand encryption #1070
|
Hi everyone, Trying to migrate from dotenvx local priv-pub-key encryption to varlock. If I understand this correctly, if I use hardware backed encryption, that exact hardware is necessary to decrypt secrets (including from backups) on a new machine. Does that mean using file based encryption will ensure recoverability from backups on a new machine? I want to be sure secrets are recoverable from backups as long as I backup the env files and config directory. Or maybe there is a way to decrypt secrets while using hardware backed encryption using backup keys or recovery keys on a new hardware? The docs don't seem to care about recoverability at all and assumes the user is using another secrets management tool to store secrets long term. Do I understand this correctly? |
Replies: 1 comment
|
Local encryption is meant to be for a single machine, to get local overrides (like |
Local encryption is meant to be for a single machine, to get local overrides (like
.env.localsecret zero type items) out of plaintext. We're actively working on extending this to team vaults.