Ticket #29441 (new defect)
dsniff-devel compiles but does not work on snow leopard
| Reported by: | tribes_email@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ||
| Port: | dsniff-devel |
Description
I've played with it for a few days, tried to compile my own version (I have tried 2.3 and 2.4b1) not matter what I always reproduce the same problem.
arpspoof works
but apps like dsniff, urlsnarf don't see anything on the network. They don't crash but never log anything. I think this is due to some snow leopard limitation for non blocking observation of the network. I'm not sure.
Change History
comment:1 Changed 2 years ago by macsforever2000@…
- Keywords dsniff urlsnard libpcap libnet libnids removed
- Port set to dsniff-devel
comment:2 Changed 2 years ago by ryandesign@…
Have you tried contacting the developer of dsniff about this? We have no maintainer for dsniff in MacPorts.
comment:3 Changed 2 years ago by jmr@…
There doesn't appear to have been any upstream development since 2002.
comment:4 Changed 2 years ago by tribes_email@…
Exactly the development stopped a long a time ago so I guess it's over for dsniff support on snow leopard. Just by curiosity I compiled dsniff and ran it in a linux vmware on my macbook and it works ?! So there is definitely some incompatibility with osx. I tried briefly to debug the dsniff code. It appears dsniff does not receive any information so the problem probably lies in the lib it uses.
comment:5 Changed 2 years ago by tribes_email@…
It seems that drifnet faces the same problem. Does not crash but does not detect anything on the network. I think the only lib common to driftnet and dsniff is libpcap so maybe the problem lies here. So I guess any application using lipcap could have the same issue