On 08/30/2019 11:06 AM, Carlos E. R. wrote:
On 30/08/2019 16.40, Lew Wolfgang wrote:
On 2019-08-30 08:36, Carlos E. R. wrote:
Well, you have to run the daemon on one end and the application on another. He's been doing that all the time (rshd)
I did not know this was not encrypted transfer. rsync has never had encryption. It's add on via ssh and such. Interesting! I never thought of running the rsync daemon. It would have to be running on all of our hosts to mimic our current setup, and the "modules" would have to be
On 08/29/2019 11:57 PM, Bengt Gördén wrote: figured out. I guess that if authentication is enabled, that username/passwords are sent in the clear, right? They are not the account passwords, they are either typed or kept on separate files on both server and client. I don't know if they are sent on the clear or not.
Ah, so used this way the rsync server is functioning like an ftp server. Our usage case with ssh and rsh (in the enclave) is for users to read/write in their home directories, or common areas with suitable permissions. Again, maybe pre-placed secrets with munge is the easiest way forward? BTW, I checked and the 40-GbE interfaces we have don't support iWARP, so nfs via rdma won't work unless we update our NIC's. I'm sure I can convince management to purchase some, I'll report my progress here as time goes by. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org