From e33a497573d522c1ded7158a11b3b1314d62ac73 Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Thu, 27 Oct 2022 08:54:58 +0200
Subject: Added some notes on permissions

---
 topics/systems/backup-drops.gmi | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/topics/systems/backup-drops.gmi b/topics/systems/backup-drops.gmi
index 84c1612..4fd916b 100644
--- a/topics/systems/backup-drops.gmi
+++ b/topics/systems/backup-drops.gmi
@@ -48,7 +48,15 @@ And run
 systemctl reload ssh
 ```
 
-You may need to add to allowusers for ssh access.
+You may need to add to allowusers for ssh access. If you use allowusers (recommended) you can even specify the sending host with
+
+```
+AllowUsers bacchus@remote
+```
+
+where remote can be an IP address.
+
+Warning: if you introduce this `AllowUsers` command all users should be listed or people may get locked out of the machine.
 
 Next create a special key on the backup machine's ibackup user (just hit enter):
 
@@ -113,4 +121,10 @@ touch ~/mnt/dropserver/drop/HELLO
 
 And the remote directory should be ready for dropping files!
 
+To unmount the dir
+
+```
+fusermount -u ~/mnt/dropserver
+```
+
 IMPORTANT: it is important to try ssh and read /var/log/auth.log to deal with permission issues. sshfs and the underlying sftp protocol are fussy.
-- 
cgit v1.2.3