Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

key add, key passwd: Allow new password via scripting #827

Closed
robbat2 opened this issue Feb 25, 2017 · 4 comments
Closed

key add, key passwd: Allow new password via scripting #827

robbat2 opened this issue Feb 25, 2017 · 4 comments
Labels
type: feature enhancement improving existing features

Comments

@robbat2
Copy link

robbat2 commented Feb 25, 2017

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

@robbat2 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 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
@fd0
Copy link
Member

fd0 commented Feb 27, 2017

Hey, thanks for suggesting this. Could you please describe your use case?

@fd0 fd0 added the type: feature enhancement improving existing features label Feb 27, 2017
@robbat2
Copy link
Author

robbat2 commented Mar 2, 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).

@fd0
Copy link
Member

fd0 commented Mar 2, 2017

Thanks for the explanation, that makes sense.

@HLeithner
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature enhancement improving existing features
Projects
None yet
Development

No branches or pull requests

3 participants