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
{{ message }}
Repository navigation
Allow changing repository password from the UI
#1369
Currently, the repository password field is disabled when editing an existing repository — but the current value is still visible and copyable via the eye icon next to the field. So the lock doesn't protect against accidental exposure; it just blocks changing a value that's already fully visible anyway.
Current workaround
Run restic key passwd manually to re-encrypt the master key with a new password: restic -r <repo-uri> key passwd
Manually update the stored password in Backrest so it can keep authenticating on scheduled runs — either by editing config.json directly, or by unlocking the disabled field via browser devtools.
Both work, but this is fragile (config.json editing has no validation) and not discoverable for less technical users.
Proposed feature
A "Change Password" action on the repository page that:
Prompts for the new password
Internally runs restic key passwd (or key add + key remove for the old key) using the repo's stored connection details
Updates the stored password in the config automatically on success
Since Backrest already shells out to restic for other operations (snapshots, diff, prune, check), this seems like a small addition on top of existing plumbing — and it would remove any need for manual config.json editing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
Currently, the repository password field is
disabledwhen editing an existing repository — but the current value is still visible and copyable via the eye icon next to the field. So the lock doesn't protect against accidental exposure; it just blocks changing a value that's already fully visible anyway.Current workaround
restic key passwdmanually to re-encrypt the master key with a new password:restic -r <repo-uri> key passwdconfig.jsondirectly, or by unlocking the disabled field via browser devtools.Both work, but this is fragile (
config.jsonediting has no validation) and not discoverable for less technical users.Proposed feature
A "Change Password" action on the repository page that:
restic key passwd(orkey add+key removefor the old key) using the repo's stored connection detailsSince Backrest already shells out to restic for other operations (snapshots, diff, prune, check), this seems like a small addition on top of existing plumbing — and it would remove any need for manual
config.jsonediting.All reactions