From: not@telling.you.invalid   
      
   Carlos E.R.  wrote:   
   > On 2026-01-17 01:52, Computer Nerd Kev wrote:   
   >> Carlos E.R.  wrote:   
   >>> 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?   
   >>>   
   >>> AFAIK yes, the transfer happens of the ssh port with ssh type of   
   >>> encryption.   
   >>   
   >> If you use "rsync://" on the client command line, you're connecting   
   >> to rsyncd using the Rsync protocol which doesn't use encryption,   
   >> which I often do for LAN transfers. You could still use SSH   
   >> tunneling for encryption of course.   
   >   
   > I am using the rsync:// syntax, and I don't remember opening another   
   > port than 22. :-?   
      
   According to the man page it's TCP port 873.   
      
   Anyway I think it makes much more sense than dealing with all the   
   complexities, fragilities, and inefficiencies of encryption just   
   to do transfers over a private LAN. LDO evidently concludes the   
   opposite.   
      
   Here's an example of a public rsync 'site'. This command lists   
   syncable directories and their descriptions:   
      
   rsync rsync://mirrors.dotsrc.org   
      
   This page also describes how it can use TLS encryption using a   
   script for OpenSSL "s_client", but that's not part of the base   
   protocol:   
      
   https://dotsrc.org/mirrors/#rsync-over-tls   
      
   --   
   __          __   
   #_ < |\| |< _#   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)