From e8c6d086a6331fdf68876ea8ce178b9c40bf407c Mon Sep 17 00:00:00 2001 From: DatuX Date: Mon, 22 May 2023 13:16:43 +0200 Subject: [PATCH] Updated Home (markdown) --- Home.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Home.md b/Home.md index e45edab..41de338 100644 --- a/Home.md +++ b/Home.md @@ -203,17 +203,18 @@ Note that this is called a "pull" backup. The backup (target) machine pulls the It is also possible to let a source machine push its backup to the target machine. There are security implications to both approaches, as follows: -With a pull backup, the target machine will have ssh access to the source machine. - -With a push backup, the source machine will have ssh access to the target machine. +* With a pull backup, the target machine will have ssh access to the source machine. +* With a push backup, the source machine will have ssh access to the target machine. If you wish to do a push backup, then you would setup the SSH keys the other way around and use the `--ssh-target` parameter on the source machine. +Note that you can always change the ssh source and target parameters at a later point without any problems. + #### Pull+push (zero trust) It also possible to use a 3rd server that pulls backups from the source and pushes the data to the target server via 1 stream. This way the source and target server wont have to be able to reach each other. If one server gets hacked, they cant access the other server. -To do this, you have to install zfs-autobackup on a 3rd server and use both `--ssh-source` and `--ssh-target` to specify the other servers. +To do this, you only have to install zfs-autobackup on a 3rd server and use both `--ssh-source` and `--ssh-target` to specify the other source and target servers. ### Local Usage