Not to mention, due to the fact that SSH uses more bandwidth, if there's any sort of packet lose, SSH can basically be rendered unusable. Telnet on the other hand isn't. SSH also sends traffic when it's idle, telnet does not.
Telnet has it's place in corporate IT, but, for the most part, it should be avoided on home networks that are Internet ready. But if a strong firewall is in place, or a telnet proxy is being used, telnet can be very handy. However, I still prefer SSH. tdh -- -------------------------------------------------------------------- T. Holmes | UNIXTECHS.org | [EMAIL PROTECTED] | UIN: 17021091 -------------------------------------------------------------------- | Michael, | | Actually, on a previous thread there were a (large) number | of reasons, including printers, emulators, switches, routers... | a whole bestiary of equipment which does not speak ssh | but telnet. Not to mention a plethora of platorms, and the | conditions under which an unencrypted telnet can be used | with minimal risk. | | See previous thread 'Arrrgh - Telnet Problems (Authentication?)' | for your edification (and a solution). | | Regards, | David | | P.S. skidley (Chad?) - apology accepted. | | -- | | "Entropy Requires No Maintenance" | | Want to buy your Pack or Services from MandrakeSoft? | Go to http://www.mandrakestore.com -----------------------------Uptime ------------------------------- 7:15PM up 22 days, 7:55, 2 users, load averages: 0.00, 0.02, 0.00 -------------------------------------------------------------------
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
