From a41ec5b34b406d9329c55be85d6be6aabbc6efde Mon Sep 17 00:00:00 2001 From: metamuffin Date: Fri, 14 Jun 2024 05:05:56 +0200 Subject: mention alternative iimplementation ideas --- readme.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/readme.md b/readme.md index 49b72b5..7e49cd2 100644 --- a/readme.md +++ b/readme.md @@ -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: -- cgit v1.2.3-70-g09d2