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
I am running backups on a system without a keyring. Whenever I initialize a repository with b2 storage and enabled encryption, I have to enter three different secrets
However, when setting up many repositories, entering the three secrets a second time is cumbersome and error prone.
I would greatly appreciate an option -store-credentials-in-plain-text (or similar) on the init command, that does the three set -key .. -value .. commands for me.
The text was updated successfully, but these errors were encountered:
What type of system are you running it on? I had a similar issue on a Synology, which didn't have typical linux keyring, and I solved it by using keyctl to store the secrets and then using a script to read them and export as environment variables prior to the duplicacy commands being run. Here's some more info on it in case it may be useful.
I am running backups on a system without a keyring. Whenever I initialize a repository with b2 storage and enabled encryption, I have to enter three different secrets
Then, when I backup, I have to enter those credentials again. For automated backups, I follow the steps for managing passwords in the preferences file (plain text).
However, when setting up many repositories, entering the three secrets a second time is cumbersome and error prone.
I would greatly appreciate an option
-store-credentials-in-plain-text
(or similar) on theinit
command, that does the threeset -key .. -value ..
commands for me.The text was updated successfully, but these errors were encountered: