diff options
| author | metamuffin <metamuffin@disroot.org> | 2024-06-14 05:05:56 +0200 |
|---|---|---|
| committer | metamuffin <metamuffin@disroot.org> | 2024-06-14 05:05:56 +0200 |
| commit | a41ec5b34b406d9329c55be85d6be6aabbc6efde (patch) | |
| tree | 5dd6fa628d967fa1453ca3cfbfdb59e612de83af | |
| parent | 23d3316b8c158847f7f4bb34fae49ed658058b68 (diff) | |
| download | online-offsite-backup-a41ec5b34b406d9329c55be85d6be6aabbc6efde.tar online-offsite-backup-a41ec5b34b406d9329c55be85d6be6aabbc6efde.tar.bz2 online-offsite-backup-a41ec5b34b406d9329c55be85d6be6aabbc6efde.tar.zst | |
mention alternative iimplementation ideas
| -rw-r--r-- | readme.md | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -30,6 +30,15 @@ connections it makes: You **must** implement protection on this level yourself. Backups are stored as-is on the remote server: If your backup requires it, encrypt it! +Alternative Implementations: There are other ways to implement the functionality +of this tool. I specifically considered creating system user accounts whose +login shell is set to something custom for each peer so they can be automatated +over SSH (which would deal with encryption for me) - that idea was discarded +because it feels too much like security layers are not clear-cut when using SSH +for semi-untrusted operations. A read-write network filesystem with a script +copying backups to a safe location outside of the shared FS could work too but +requires some effort to implement for multiple users. + ## Usage 1. Intall the CLI with cargo: |