-
balian0 : The entire conversation between the telnet client and server is clear text. So any sniffer or box in between can read the packets that go through (also username and password). Like K-line said, he has important stuff on his machines, so using telnet is not the solution. SSH is where the entire conversation between client and server is encrypted, so if someone was to sniff the packets, they would only get garbage on their screens. Thats why there is such a thing as SSH.
Cheers.
Evidence: You really have no idea what your talking about, do you ??? (After reading your post in the tutorials section, it amazing what stuff you come up with.) :p
-
Quote:
Originally posted here by balian0
what's so insecure about telnet ?
I guess another question you could ask is, what is secure about telnet? which is nothing. All information transmitted in a telnet session is sent in the clear.
-
[quote]: balian0- what's so insecure about telnet ?
it send the information in raw, which means passwds and such can be sniffed easily, SSH crypts it, which is altogether more secure (if you keep it patched)
Preep
-
You can set up a secure telnet server easily - ensure that noone from a nontrusted network or via a nontrusted network ever connects to it via either IP restrictions in the telnet server itself, or filtering at the OS level (i.e. firewalling)
Other than that take normal precautions to prevent them from being able to gain any more access than you give them.
If you want people from or via nontrusted networks to be able to connect, use something else.
