Date: Thu, 26 Mar 2009 18:34:27 -0700 From: Julian Elischer <julian@elischer.org> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: barney_cordoba@yahoo.com, Ruben de Groot <mail25@bzerk.org>, Ian FREISLICH <ianf@clue.co.za>, Chuck Robey <chuckr@telenix.org>, current@FreeBSD.org Subject: Re: Telnet root login Message-ID: <49CC2D23.5080000@elischer.org> In-Reply-To: <49CC2B14.10408@FreeBSD.org> References: <995845.90009.qm@web63905.mail.re1.yahoo.com> <E1LmSXe-000IqH-QM@clue.co.za> <49CA6754.4030302@elischer.org> <49CC2B14.10408@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev wrote: > Julian Elischer wrote: >>> Then use ssh and set "PermitRootLogin yes" in /etc/ssh/sshd_config >> >> this doesn't work if you are usinf a set of machines run from a >> central machine using nc (netcat) to do scripted i/o through a telnet >> session on the other machines (for example). >> >> The advantage of telnet is you can pipe nc straight into it. > > Dude, ssh with password-less master key on client and correct > certificate on server in ~/authorized_keys2 is your friend. You can pipe > right to ssh in scripts just fine and it's all nice and secure. You can > also do other interesting things with port forwarding over ssl link. I expressed myself poorly I want to pipe straight tcp into sessions for remote control I often use the method you describe above, but sometimes it's just too cumbersom. > > -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49CC2D23.5080000>