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
Is your feature request related to a problem? Please describe.
I would like to create backups of non-confidential files without password encryption.
Describe the solution you'd like
Since restic 0.17, the --insecure-no-password flag has been supported to allow creation of repos without password encryption. It would be great if Backrest could support this flag also.
Right now if I try to create a repo without a password, I get an error message saying
Missing repo password. Either provide a password or set one of the env variables RESTIC_PASSWORD, RESTIC_PASSWORD_COMMAND, RESTIC_PASSWORD_FILE.
Perhaps there can be a checkbox for disabling the password? Alternatively, if the goal is to discourage passwordless backups, could the error condition be updated to allow no password to be set when --insecure-no-password is added as a flag?
Thank you!
The text was updated successfully, but these errors were encountered:
This should be supported out of the box by the daemon. I'm about to leave on vacation so I won't get to this for a few weeks, but it should be very straightforward.
Is your feature request related to a problem? Please describe.
I would like to create backups of non-confidential files without password encryption.
Describe the solution you'd like
Since restic 0.17, the
--insecure-no-password
flag has been supported to allow creation of repos without password encryption. It would be great if Backrest could support this flag also.Right now if I try to create a repo without a password, I get an error message saying
Perhaps there can be a checkbox for disabling the password? Alternatively, if the goal is to discourage passwordless backups, could the error condition be updated to allow no password to be set when
--insecure-no-password
is added as a flag?Thank you!
The text was updated successfully, but these errors were encountered: