mirror of
https://github.com/restic/restic.git
synced 2024-12-23 00:07:25 +00:00
doc: Add --cacert to REST section
This commit is contained in:
parent
6a4a328bbc
commit
abde9e2fba
1 changed files with 5 additions and 4 deletions
|
@ -135,10 +135,11 @@ are some more examples:
|
|||
$ restic -r rest:https://user:pass@host:8000/
|
||||
$ restic -r rest:https://user:pass@host:8000/my_backup_repo/
|
||||
|
||||
If you use TLS, make sure your certificates are signed, 'cause restic
|
||||
client will refuse to communicate otherwise. It's easy to obtain such
|
||||
certificates today, thanks to free certificate authorities like `Let’s
|
||||
Encrypt <https://letsencrypt.org/>`__.
|
||||
If you use TLS, restic will use the system's CA certificates to verify the
|
||||
server certificate. When the verification fails, restic refuses to proceed and
|
||||
exits with an error. If you have your own self-signed certificate, or a custom
|
||||
CA certificate should be used for verification, you can pass restic the
|
||||
certificate filename via the `--cacert` option.
|
||||
|
||||
REST server uses exactly the same directory structure as local backend,
|
||||
so you should be able to access it both locally and via HTTP, even
|
||||
|
|
Loading…
Reference in a new issue