Message-ID: <6ac4741b@news.ausics.net> From: Computer Nerd Kev Subject: Re: Another ssh quirk... Newsgroups: comp.os.linux.misc References: <11a05ig$2pnll$1@news.xmission.com> <6ac430ec@news.ausics.net> User-Agent: tin/2.6.5-20251224 ("Glenury") (Linux/2.4.31 (i686)) NNTP-Posting-Host: news.ausics.net Date: 6 Oct 2026 14:07:55 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 27 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:92993 Carlos E. R. wrote: > On 2026-10-06 01:21, Computer Nerd Kev wrote: >> Kenny McCormack wrote: >>> Yes, I enjoy writing about these weird quirks that I find in the ssh tools >>> (including rsync). I find it amusing that ssh (and friends) - a tool we >>> all use daily and rely on heavily - is still stuck, design-wise, in the >>> 1980s. >> >> I just double-down on the 1980s mindset and use Telnet instead of >> SSH for talking to things like Raspberry Pis which are on my own >> LAN where nobody should be able to listen/connect anyway, unless >> they can just walk over and steal its SD card anyway. Makes >> everything much simpler, once you've installed the Telnet server. > > telnet does not send files, AFAIK. No more than SSH does, on its own. But if you want an equivalent set of "and friends" that don't over-complicate things with unnecessary security, look through the programs in GNU Inetutils. Plus Rsync isn't just an "ssh tool" at all, as the OP suggested - I frequently use the Rsync protocol which is unencrypted, and if you use Rsh instead of Telnet that can work with Rsync unencrypted too. I also use FTP a lot. -- __ __ #_ < |\| |< _#