You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
restic -p argument uses the same password for the new key as the existing key.
See also #826 that wants to add consistent manual selection of keys
The text was updated successfully, but these errors were encountered:
robbat2
changed the title
key add, key password: Allow new password via scripting, allow selection of key
key add, key password: Allow new password via scripting
Feb 25, 2017
robbat2
changed the title
key add, key password: Allow new password via scripting
key add, key passwd: Allow new password via scripting
Feb 25, 2017
Use case: Using an S3 repo, I'd like an administrative host to be able (scriptable) to create a number of keys with unique passphrases, one for each host being backed up.
Better yet would be to say that the later keys are permitted to do backups, but not change any settings (or restore, but that's into the realm of asymmetric keys).
Output of
restic version
restic 0.4.0
compiled with go1.6.2 on linux/amd64
Expected behavior
Restic should be fully scriptable to add a new key or rotate the password of a key:
restic -p $OLD_PASS_FILE key add --new-password-file $NEW_PASS_FILE
restic -p $OLD_PASS_FILE key passwd $ID --new-password-file $NEW_PASS_FILE
Actual behavior
restic -p
argument uses the same password for the new key as the existing key.See also #826 that wants to add consistent manual selection of keys
The text was updated successfully, but these errors were encountered: