-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Open
Labels
Description
Any call to fdbbackup modify is such that:
There is no encryption flag in the command, so it is not possible to specify an encryption key for it.
Any encryption key associated with the existing backup gets dropped.
This is undesirable and unexpected because:
- Backups that were previously encrypted become unencrypted after modification, exposing sensitive data.
- The absence of a warning or explicit action means users may inadvertently compromise backup security without realizing it.
- This behavior is inconsistent with typical expectations that modifications should preserve existing security settings unless explicitly changed.
Ideally, fdbbackup modify should either preserve the existing encryption key by default or provide an option to specify or update the encryption key during modification. This would ensure backup security is maintained throughout the backup lifecycle.
akankshamahajan15