From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by AlpΓ‘r-Etele MΓ©der, licensed under CC BY 3.0
So... As long as you have ssh running open on the receiving server, you don't need the rsync daemon. Rsync client will ssh, then execute rsync recipient automatically.
The daemon is only for if you don't want to or cannot run ssh really.
Is there a specific reason you are looking at the daemon, or just unfamiliar?
Using the daemon also allows you to transfer faster by removing compression and encryption. It tends to hit the same rclone speeds without the data corruption issues.
You can do so directly in the ssh config or command line also. I've used this very thing in dense cluster private OpenStack deployments over the years.
Just trying to narrow down use case but I suspect the complex documentation just overwhelmed.
(disclaimer: this information might be years out of date but i think it is still accurate?)
SSH doesn't have a null cipher, and if it did, using it still wouldn't make an SSH tunnel as fast as a TCP connection because SSH has its own windowing mechanism which is actually what is slowing you down. Doing the cryptography at line speed should not be a problem on a modern CPU.
Even though SSH tunnels on your LAN are probably faster than your internet connection (albeit slower than LAN TCP connections), SSH's windowing overhead will also make for slower internet connections (vs rsync or something else over TCP) due to more latency exacerbating the problem. (Whenever the window is full, it is sitting there not transmitting anything...)
So, to answer OP's question:
--rsh=ssh as that is the default).man rsync and read the section referred to by this:
The remote-shell transport is used whenever the source or destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an rsync:// URL is specified (see also the USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION section for an exception to this latter rule).
HTH.
I've been doing the same in pull-backups for years. It works nicely.
The statement is correct, rsync by itself doesn't use ssh if you run it as an daemon and if you trigger rsync over ssh then it doesn't use daemon but instead starts rsync with UID of the ssh-user.
But, you can run rsyncd and bind it only to localhost and connect to that over ssh-tunnel. That way you can get benefits of rsync daemon and still have encrypted connection with ssh.
Thank you @IsoKiero@sopuli.xyz !
This is the solution.
unfortunately I can't apply it, because the NAS is a closed proprietary π©
I think you don't need to specify that you want to use SSH. unless you give the location as starting with rsync://, or set to use the rsh protocol, it should use ssh by default.
just use user@targethost:path. The part before : is the same as what you use in SSH, and the part after it may be an absolute or a relative (to user home) path
Given that you can already use rsync over ssh, I suspect you want to allow the rsync configuation options on the server side, but still use ssh to secure the transit. I would do it like this:
That would encrypt the traffic over your ssh tunnel, but still allow you to use the receiver's rsyncd paths.
So there is no way with Rsync (under ssh) to set settings (config file or other) that will apply to all clients !!??
So it's the client that configure rsync and the server !? there is no way around ?!
You basically want to use the daemon but under ssh. I looked into this before, and I think it is possible but the command for it is weird and confusing. Wish I remembered it, but just commenting to say that I vaguely remember there's a way (or maybe I'm hallucinating).