Update README.md
This commit is contained in:
parent
98cb7f5822
commit
7664fa1b33
@ -53,10 +53,13 @@ It's possible to use a remote server as destination for the backup. Just use the
|
||||
For this to work, rsync must be installed on the server too.
|
||||
|
||||
### Server authentication
|
||||
Right now only authentication using SSH key works. If an ssh-agent is running on your system, available ssh keys will be used automatically. Otherwise, it's possible to specify the key location with --keyfile or in the configuration file. Note that if no ssh agent is running, it might be necessary to unlock the private key more than once.
|
||||
Right now only authentication using SSH key works. The best way to handle the authentication is to have an ssh agent running on your system, otherwise if a passphrase is necessary to unlock the ssh key, it will be necessary to enter it more than once.
|
||||
If needed, it's possible to specify the ssh key location with the --keyfile argument or in the configuration file.
|
||||
|
||||
To be able to connect to the user authentication agent when running simple_backup with sudo, use:
|
||||
To be able to connect to the user's ssh agent when running simple_backup with sudo, make sure to preserve the SSH_AUTH_SOCK environment variable. For example:
|
||||
|
||||
```bash
|
||||
sudo --preserve-env=SSH_AUTH_SOCK -s simple_backup [options]
|
||||
```
|
||||
|
||||
or by editing the sudoers file.
|
||||
|
Loading…
x
Reference in New Issue
Block a user