View Single Post
Posts: 28 | Thanked: 7 times | Joined on Mar 2007 @ Eastern U.S.A.
#8
Originally Posted by pixelseventy2 View Post
because for a quick test telnet is much quicker than netcat, especially if I don't care about the output. For example, to test if a TCP port on a remote machine is accessible or not, "telnet 10.10.10.10 8009" is a quick and easy test.

Plus, I'm not a sys-admin, fluent in the ways of netcat, and I have to lookup how to use it again every time
No disrepect intended to the original author of netcat, who is an old friend of mine, but I'm with pixelseventy on this one.

I couldn't live without quickly dashing off telnet connections to arbitrary ports, and yes, I know the protocol spec enough to know that there is a likelihood that things can be send in the setup handshake that might introduce garbage into the connection. I probably have cause to do it at least 10 times a day.

GA is right to encourage people to use secure tools for remote access though.

It's fast, and present on pretty much anything I sit down at. Time is money.