From: vallor@vallor.earth   
      
   At Mon, 19 Jan 2026 14:27:28 +0100, "Carlos E.R."   
    wrote:   
      
   > On 2026-01-19 12:45, Pancho wrote:   
   > > On 1/17/26 18:20, The Natural Philosopher wrote:   
   > >> On 17/01/2026 13:11, Richard Kettlewell wrote:   
   > >>> "Carlos E.R."  writes:   
   > >>>> On 2026-01-16 15:57, The Natural Philosopher wrote:   
   > >>>>> On 16/01/2026 12:48, Carlos E.R. wrote:   
   > >>>>>   
   > >>>>>> scp -- wrong. rsync, scp and sftp are all different ways of   
   > >>>>>> transferring files securely over SSH.   
   > >>>>> Are they? even if you run  rsyncd?   
   > >>>   
   > >>> If you tell it to connect to an rsyncd then indeed it does not   
   > >>> use SSH.   
   > >>>   
   > >>> Personally I have never bothered with rsyncd...   
   > >>>   
   > >> Ah. I do. None of my data is private that is being stored remotely   
   > >>   
   > >>>> AFAIK yes, the transfer happens of the ssh port with ssh type of   
   > >>>> encryption. That is what the article says, so take it with a   
   > >>>> pinch of salt. Variances per distributions. It is true in   
   > >>>> openSUSE.   
   > >>>   
   > >>> The zdnet article says nothing about what protocol rsync uses.   
   > >>>   
   > >> I think it is straight streaming of bytes and that is it.   
   > >> Locally i have nfs mounts to move data around.   
   > >>   
   > >> So I don't really use ssh protocols to copy data at all.   
   > >>   
   > >>   
   > >   
   > > I'm currently looking at moving from backing up data on Samba   
   > > shares, to ssh/rsync (due to symlink issues). I fell at the first   
   > > hurdle of how to have root access on both local and remote host.   
   > > Eventually I created a new remote user account with passwordless   
   > > sudo, specifically for rsync. The solution seemed a bit crap. It   
   > > seemed that such a common usecase should be better documented, like   
   > > I was missing something.   
   > >   
   >   
   > You can configure to access ssh as root without typing a password.   
   > With key pairs, and have an agent remember the phrase for you, or   
   > have none.   
      
   I thought I'd jump in here, and point out that you can have   
   a passphraseless secret key on the client, and set the key   
   in authorized_keys to only be able to run a single command   
   (or a set of commands).   
      
   > > Does rsyncd solve this root access problem? Is it a better/more   
   > > orthodox solution.   
   >   
   > Yes, rsyncd does this.   
      
   Regarding rsyncd, you should have a client program, rsync-ssl   
   installed:   
      
   $ apt-file search -x ^/usr/bin/rsync-ssl$   
   rsync: /usr/bin/rsync-ssl   
      
   However, I believe you have to set up an ssl proxy like nginx   
   to handle the SSL/TLS.  See the section "SSL/TLS Daemon Setup"   
   in rsyncd.conf(5) for how to do that.   
      
   --   
   -v System76 Thelio Mega v1.1 x86_64 Mem: 258G   
      OS: Linux 6.18.5 D: Mint 22.3 DE: Xfce 4.18 (X11)   
      NVIDIA GeForce RTX 3090Ti (24G) (580.105.08)   
      "There's my way, and then there's the easy way."   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)