IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Extensions to SSH in order to facilitate telnet replacement.
As opposed to building the telnet complexities into sshd? And of course
every device for which this functionality would be desired already has
the telnet server built in. Ditto telnet client, for ssh clients.
Maybe I misunderstood the request, but it seemed clear to me that the
only motivation was to talk to things that expected to be talking via
telnet.
Barney
On Sat, Mar 02, 2002 at 11:58:07AM -0800, Joseph Galbraith wrote:
> Well, it requires running a complicated
> server (telnetd) with all it's additional
> bugs and security vulnerabilities on your
> server, and requires the client to have
> another complicated (maybe expensive?)
> piece of code on his/her system.
>
> Or, imagine either your server or
> client are dedicated devices -- now
> a telnet server seems even less
> attractive.
>
> - Joseph
>
> > Is there a reason, aside from elegance, that simply forwarding to
> > localhost (or lo0) port 23 over ssh is unacceptable? It has the
> > great advantage that no client enhancement is required.
Home |
Main Index |
Thread Index |
Old Index