Hi,
I successfully compiled dsniff 2.3, the BSD-db 3.1.17, libnids 1.13-1 and libnet
1.0.1b, as well as openssl 0.9.6 on a suse 7.0 installation with kernel 2.2.16.
Build problems with suse 6.4 may be caused by an outdated libnet installation.
Consult the dsniff faq www.monkey.org/~dugsong/dsniff/faq.html for further
information.
First I had similar troubles getting dsniff into action - it did not catch
anything. Then I forced dsniff in "magic" mode and used eth0 explicitly. The
command line reads: dsniff -m -i eth0 . Afterwards the packets started to roll
in, even from hosts other than the dsniff machine in the same subnet (I tried
it with ftp, telnet, pcanywhere and pop3).
Boris
On Tue, 19 Dec 2000 10:49:23 +0100, you wrote:
"SecurityPortal has a very interesting article by Kurt Seifried in which he writes "dsniff 2.3 allows you to exploit several fundamental flaws in two [snip]
Does anyone have dsniff 2.3 running on Suse 6.4? I just tried to compile
I tried dsniff some time ago. It compiled perfectly, appropiate libs included. But I noted that it doesn't work very well.
1) I telneted to another machine (in the same lan-segment as mine) and dsniff didn't catch anything. I telneted to my own machine (the one running dsniff) and then it caught well. Why? Please note that other sniffers like Sniffer Pro (on WinNT, same machine [dual boot]) works perfectly: they catch ALL traffic, include the one to other local machines. I mean, it's no problem of switching. 2) Repeating the former proccess, user/pass is not catch in all cases. It shows like a bit random behaviour.
Comments? [...]