Hello @jadudm
@jadudm said in Extremely slow backups to Hetzner Storage Box (rsync & tar.gz) – replacing MinIO used on a dedicated Cloudron:
Cloudron always changes the permissions on the directory /home/pool/dataset/cloudback to 777. This seems... grossly insecure.
This behaviour is comming from SSHFS itself since Cloudron has to set the SSHFS option allow_other and this will set the path e.g. /mnt/cloudronbackup to 777.
From the SSHFS manual - https://man7.org/linux/man-pages/man1/sshfs.1.html :
By default, only the mounting user will be able to access the filesystem. Access for other users can be enabled by passing -o allow_other.
In your example without allow_other only the user cloudback would be able to access the mount.
@jadudm said in Extremely slow backups to Hetzner Storage Box (rsync & tar.gz) – replacing MinIO used on a dedicated Cloudron:
And, worse, it breaks SSH, because you can't have a filesystem above the .ssh directory with permissions that open.
Is that really the case?
I am running a Cloudron server with a Hetzner Storage Box as the backup provider with SSHFS.
In the home there is .ssh/authorized_keys which gives access to the whole Storage Box.
There also is a sub-folder named storage_volume01 which I use for a volume mount with SSHFS which also has a .ssh folder, but with a Hetzner Storage Box Sub-Account.
This is working without any issues.
Do you mean this breaks ssh on the target system?
