Eric H. Johnson wrote: > Les, > > The passwords are passed as plain text, so a determined hacker would not > have much difficulty sniffing out the passwords. One option for increasing > security over the Internet is to run the telnet session over an ssh > connection. That way all transactions will be encrypted and it adds an > additional password layer. The telnet socket could then be blocked at the > router or firewall, and only allow the ssh socket through. > > Regards, > Eric > > > One good security measure is to change the port number. First the hacker has > to find your port then they have to crack the password (obviously don't use > the standard password). Of course that assumes you want to connect remotely > over the internet (why???). Otherwise just block the port on your firewall. >
telnet for communications in 2009? Like Eric pointed out, using a tunnel lessens the possibility of a break in but you still have to run telnet daemon either standalone or from inetd on the receiving end, socketed or not. Why not use SSL? That would not require changes on the receiving end. See sclient http://www.rtfm.com/openssl-examples/ There is tons more. Search "SSL example" If no other tools are available, telnet is good for one thing: test for a listening port. Most of the time you can't tell more than system is listening on it or not. telnet <somehost> <port number> -- Rafael ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
