Step 23: TLS transport for sgardd and sgard client.
Server: --tls-cert/--tls-key flags enable TLS (min TLS 1.2). Client: --tls enables TLS transport, --tls-ca for custom CA certs. Two integration tests: push/pull over TLS, reject untrusted client. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
18
README.md
18
README.md
@@ -185,6 +185,24 @@ sgard pull --remote myserver:9473
|
||||
Authentication uses your existing SSH keys (ssh-agent, `~/.ssh/id_ed25519`,
|
||||
or `--ssh-key`). No passwords or certificates to manage.
|
||||
|
||||
### TLS
|
||||
|
||||
To encrypt the connection with TLS:
|
||||
|
||||
```sh
|
||||
# Server: provide cert and key
|
||||
sgardd --tls-cert server.crt --tls-key server.key --authorized-keys ~/.ssh/authorized_keys
|
||||
|
||||
# Client: enable TLS (uses system CA pool)
|
||||
sgard push --remote myserver:9473 --tls
|
||||
|
||||
# Client: with a custom/self-signed CA
|
||||
sgard push --remote myserver:9473 --tls --tls-ca ca.crt
|
||||
```
|
||||
|
||||
Without `--tls-cert`/`--tls-key`, sgardd runs without TLS (suitable for
|
||||
localhost or trusted networks).
|
||||
|
||||
## Encryption
|
||||
|
||||
Sensitive files can be encrypted individually:
|
||||
|
||||
Reference in New Issue
Block a user