Probably because many windows users don't have the option of installing an SSH client on their own workstation due to the policy of the employer. It isn't always feasible to make other departments install an SSH client to access your system.
It would be nice if Microsoft would distribute an SSH client with windows like it does telnet, but then they would probably break it like they did telnet. -----Original Message----- From: Ryan Ware [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 7:05 AM To: [EMAIL PROTECTED] Subject: Re: What is the best way to limit Linux Telnet access to /localho st o nly Since we all know telnet is horrible in this day and age, why isn't it dropped entirely? Is there any function it can do that SSH cannot? Every time someone brings up Telnet, they are smacked down by everyone telling them find another way. Shouldn't we just end the debate and get rid of it? > -----Original Message----- > From: Alan Cox [SMTP:[EMAIL PROTECTED] > Sent: Friday, March 21, 2003 10:13 AM > To: [EMAIL PROTECTED] > Subject: Re: What is the best way to limit Linux Telnet access to > /localho st o nly > > On Thu, 2003-03-20 at 21:15, Kharnas, Simon wrote: > > Hello, Mark. > > > > I am trying to limit the telnet logon from the outside world. I thought > that > > DENY and ALLOW files can limit that access, so that the outside (i.e. > > Internet users) would not be able to logon to the server on a regular > basis. > > I still would like to allow the local users to access the host via > telnet. > > I would recommend using firewall rules rather than DENY/ALLOW as they > are stronger protections. I'd recommend exterminating telnet entirely > but providing you have total trust in anyone on your local lans, no > wireless links and so on then its obviously easier to relax and not use > encryption.
