Encrypt backups to backup_recipients with age
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
3b05ec0538
commit
12efb7d085
10 files changed
+204
-12
No files matched your search
@@ -1187,6 +1187,20 @@ The control plane publishes when the newest archive was written as
|
||||
`llmgw_backup_last_success_timestamp_seconds`, and **BackupTooOld** fires when
|
||||
it is more than 26 hours old — including when there has never been one.
|
||||
|
||||
**Encrypt them.** Name who may open them in `/etc/llmgw/server.yaml`, and every
|
||||
archive is encrypted to those keys with [age](https://age-encryption.org) and
|
||||
named `.tar.gz.age`:
|
||||
|
||||
```yaml
|
||||
backup_recipients:
|
||||
- age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p # age-keygen's public key
|
||||
- ssh-ed25519 AAAAC3Nza... ops@example # or an SSH public key
|
||||
```
|
||||
|
||||
Keep the matching private keys **off** this machine — an archive whose key
|
||||
sits beside it is not protected by it. Encrypted, a copy is safe wherever it
|
||||
lands.
|
||||
|
||||
**Copy the archives off the machine.** They sit on the disk they back up and do
|
||||
not survive losing it. Anything that copies files will do — rsync from the
|
||||
mirror, a NAS mount, an offsite bucket — as long as it keeps the archives
|
||||
@@ -1206,6 +1220,8 @@ them:
|
||||
```
|
||||
sudo systemctl stop llmgw-server
|
||||
mkdir /tmp/restore && sudo tar -xzf /var/backups/llmgw-server/llmgw-backup-<host>-<time>.tar.gz -C /tmp/restore
|
||||
# an encrypted one: open it with the private key, from wherever it is kept
|
||||
age -d -i key.txt llmgw-backup-<host>-<time>.tar.gz.age | sudo tar -xz -C /tmp/restore
|
||||
cat /tmp/restore/MANIFEST # version and time it was taken
|
||||
|
||||
# /etc/llmgw: configuration, secrets, certificates and the CA
|
||||
|
||||
@@ -185,6 +185,7 @@ rather than repeated.
|
||||
| `engines` | `map[string]string` | [Server](#server) |
|
||||
| `engine_overrides` | `[]EngineOverride` | [Server](#server) |
|
||||
| `backup_dir` | `string` | [Server](#server) |
|
||||
| `backup_recipients` | `[]string` | [Server](#server) |
|
||||
| `releases` | `string` | [Server](#server) |
|
||||
| `router` | `Router` | [Server](#server) |
|
||||
| `control` | `Control` | [Server](#server) |
|
||||
@@ -1492,6 +1493,17 @@ BackupDir is where `llmgw server backup` writes, and where the newest
|
||||
archive's age is read for llmgw_backup_last_success_timestamp_seconds.
|
||||
Empty means /var/backups/llmgw-server.
|
||||
|
||||
### `backup_recipients`
|
||||
|
||||
`[]string`
|
||||
|
||||
BackupRecipients encrypt every archive `llmgw server backup` writes, to
|
||||
whoever holds one of their keys: age recipients (age1…) or SSH public
|
||||
keys (ssh-ed25519 …, ssh-rsa …), as `age` takes them. An archive holds
|
||||
the certificate authority's key and every secret in the store, and is
|
||||
copied off the machine; encrypted, the copy is safe wherever it lands.
|
||||
Empty writes archives unencrypted, readable by root only.
|
||||
|
||||
### `releases`
|
||||
|
||||
`string`
|
||||
|
||||
Reference in new issue
Block a user