Re: ssh issue that I don't understand
<[email protected]> Wed, 8 Jul 2026 12:49:03 +0200
| Newsgroups | gmane.linux.debian.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jul 08, 2026 at 12:05:52PM +0200, Christian Groessler wrote: > Hi, > > On 7/8/26 2:24 AM, Andy Smith wrote: > > On Wed, Jul 08, 2026 at 12:36:36AM +0200, Christian Groessler wrote: > > > In "trusted local networks" one could use telnet and forget about ssh > > > overhead... > > > > I don't really follow the logic. telnet is not designed for file > > transfer but for interactive login. > > > I wasn't aware that it's about file transfer. (ftp to the rescue? :-)) The older among us know to use sz/rz for that (still in the package lrzsz). Designed to transfer binary files over channels requiring an escape layer (plus some error correction on top). But yes, nowadays I'd consider telnet mostly dead. The last legit application for a long time, using the client to interact with clear text protocol servers (http, smtp, you name them) is pretty well served by "socat -", which uses readline to edit each line before sending it. Cheers -- t
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCak4rGQAKCRAFyCz1etHa RiG1AJ9KG0olbAqmI4TLpFggXsOaGt0QpgCeMXzdzZodHmRsCFHoJsVR+kgHZz0= =E2XP -----END PGP SIGNATURE-----