Prev: Re (2): telnetd in Squeeze; was new authentication mechanism in Squeeze?
Next: how to start and run a command during boot
From: Tzafrir Cohen on 14 Jun 2010 15:50 On Mon, Jun 14, 2010 at 11:03:50AM -0700, peasthope(a)shaw.ca wrote: > From: Ron Johnson <ron.l.johnso.(a)cox.ne.> > Date: Sun, 13 Jun 2010 20:23:50 -0500 > > (Presumably you know that telnet is considered a Bad Idea Who's Time > > Has Passed?) > > Telnet is used only between machines inside my > Shorewalled network. > > > What error(s) are you getting? > > ETHNO telnetting to Squeeze. > Trying ... > dalton.invalid not opened > > Lenny telnetting to Squeeze. > peter(a)joule:~$ telnet dalton.invalid > Trying 10.4.0.2... > telnet: Unable to connect to remote host: Connection refused > peter(a)joule:~$ > > From: Mark Allums <mark(a)allums.co.> > Date: Sun, 13 Jun 2010 21:58:17 -0500 > > What about ssh? > > ssh from Lenny to Squeeze works just as well > as ever. > > > VNC? > > Have yet to try it with Squeeze. > > > RDP? > > Never used it. > > From: Tzafrir Cohen <tzafri.(a)cohens.or..il> > Date: Mon, 14 Jun 2010 12:51:46 +0000 > > Which is why Real Men use telnet, but the rest of us sane folks use ssh. > > With my clunky old hardware, telnet from Heaviside > to Joule or Dalton opens in about 1 s. ssh requires > about 15 s. I recall preferring rsh to ssh when working on s390 for the very same reason. However, one useful feature of ssh (that did not exist at the time) is that you can use one existing connection. In .ssh/config: Host * ControlMaster = auto ControlPath = ~/.ssh/control/%h__%p__%r__%l This means that the first connection to the system will have the full 15 seconds of handshaking. But the next one will simply connect on top of an existing connection. I suspect it would even be less than the 1 second for the telnet connection. If you have a number of simultanious connections, it may help. Alternatively, start a single "control connection" when you start working, and keep it working for as long as you need it. > Please don't tell me to get faster > computers unless citing a specific liability from > Shorewall. Isn't shorewall rather famous for producing not-so-efficient iptabnles rules? > > Does anyone out there have a network with at least > one machine running Squeeze? Would be nice to to > confirm the failure or hear of a successful connection. You try to login (from telnet) as root? If so: see securetty and such. -- Tzafrir Cohen | tzafrir(a)jabber.org | VIM is http://tzafrir.org.il | | a Mutt's tzafrir(a)cohens.org.il | | best tzafrir(a)debian.org | | friend -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100614194515.GN16560(a)pear.tzafrir.org.il |