Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'telnet bad, ssh good' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
telnet bad, ssh good
Authored by: macubergeek on Aug 19, '03 05:44:04PM

Why would anyone go out of their way to enable telnet which is insecure,when ssh already works, securely, with a click of a mouse button?



[ Reply to This | # ]
telnet bad, ssh good
Authored by: jollyroger on Aug 20, '03 11:48:15AM

That's easy. Some people need to access their machines remotely from within secure networks that do not allow ssh connections and only allow telnet access via proxy servers. This is a common situation in a corporate high-tech workplace environment.

I have my firewall on my home machine set up to drop all incoming telnet connections except ones from a specific host (the telnet proxy server I must go through) during certain work hours. It's not the most secure solution, but it's relatively secure and it sure beats nothing. = )

---
-monoclast



[ Reply to This | # ]
telnet bad, ssh good
Authored by: weevil on Aug 22, '03 10:17:54AM

For instance, the Newton has a telnet client but (unfortunately) not an SSH client. Rather than try to cram a bunch of software onto the Newton, it would be much cooler to telnet to a machine and use a bunch of Unix software remotely.



[ Reply to This | # ]