Output of restic version
restic 0.18.0 compiled with go1.24.4 on linux/amd64
What backend/service did you use to store the repository?
restic-server
Problem description / Steps to reproduce
Using restic key passwd --user=USER --host=HOST to change key ID and set new user/host for the key.
Expected behavior
We expect that the new key ID entry to have the user/host as specified. We also expect the output to be similar to the output of key add which emits the key ID on completion.
Actual behavior
It looks as if the user@host comes from the current user and host:
saved new key as <Key of joe@bobhost, created on 2026-03-21 06:40:42.622370569 -0700 PDT m=+9.074729872>
Do you have any idea what may have caused this?
Likely an oversight in the implementation.
Did restic help you today? Did it make you happy in any way?
Are you serious? Restic is a marvel. There are few pieces of software that are as delightful to use.
Output of
restic versionrestic 0.18.0 compiled with go1.24.4 on linux/amd64
What backend/service did you use to store the repository?
restic-server
Problem description / Steps to reproduce
Using
restic key passwd --user=USER --host=HOSTto change key ID and set new user/host for the key.Expected behavior
We expect that the new key ID entry to have the user/host as specified. We also expect the output to be similar to the output of key add which emits the key ID on completion.
Actual behavior
It looks as if the user@host comes from the current user and host:
saved new key as <Key of joe@bobhost, created on 2026-03-21 06:40:42.622370569 -0700 PDT m=+9.074729872>Do you have any idea what may have caused this?
Likely an oversight in the implementation.
Did restic help you today? Did it make you happy in any way?
Are you serious? Restic is a marvel. There are few pieces of software that are as delightful to use.