In article <62349499$0$29481$
[email protected]>,
Nicolas George <nicolas$
[email protected]> wrote:
[email protected], dans le message
<[email protected]>, a crit:
Netcat is not an sniffing tool, it's a swiss knife for networking.
At best, netcat is a letter opener for networking. If you want a Swiss Army >knife for networking, look into socat.
Indeed. I use socat when I need to do things with Unix sockets (e.g.,
fixing the bug in modern X servers where they don't listen for tcp
connections anymore). But I still use netcat for the usual TCP/UDP stuff.
As I mentioned, the real problem with netcat is that there are 70 million versions of it - so you never really know what any particular version can
or can't do (and, yes, this makes it hard to argue with strangers on Usenet about what it can and can't do). That said, I think I saw someone here
post (in defense of netcat) that it does do Unix sockets. Maybe I mis-interpreted.
Anyway, socat could be seen as just yet another member of the "netcat
family". Also, from what I can tell, something called "ncat" is actually
the best representative of that family of programs.
--
"If our country is going broke, let it be from feeding the poor and caring for the elderly. And not from pampering the rich and fighting wars for them."
--Living Blue in a Red State--
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)