parent
f4e375ad06
commit
fb7141c7ba
@ -31,4 +31,13 @@ The *seafbackup.details* file is completely annotated so you should have no prob
|
||||
- borgConnectRepo: the unified *username@url:reponame* used to access your backup provider
|
||||
- borgRepoPassphrase: the passphrase used to access your remote borg repo
|
||||
|
||||
### Note about SSH key
|
||||
|
||||
If you are planning on executing this script via cron or some other form of automation, it is highly recommended that you use an SSH key *without* a password! SSH is designed such that passwords cannot simply be passed to it via environment variables, etc. so this is something not easily automated for security reasons. As such, your computer will sit and wait for you to enter the password and will NOT execute the actual backup portion of the script until the SSH key password is provided.
|
||||
|
||||
If you really want/need to use an SSH key password, you will have to look into somethign like GNOME keyring or SSH-agent to provide a secure automated way to provide that password to SSH and allow this script to continue.
|
||||
|
||||
In practice, SSH keys without passwords are still quite safe since the key must still be known in order to connect and most keys are quite long. In addition, they key only connects to the remote server, your actual information within the borg repository is still encrypted and secured with both a key and password.
|
||||
|
||||
|
||||
That's everything you need in terms of setup. Keep reading for script parameters.
|
Loading…
Reference in New Issue
Block a user