[Lunar-bugs] [Lunar Linux 0000062]: dsniff doesnt compile with libnet-1.1

[Lunar bug reports list]

The following issue has been ASSIGNED.
======================================================================
<http://bugs.lunar-linux.org/view.php?id=62> 
======================================================================
Reported By:                wodkahexe
Assigned To:                dveatch
======================================================================
Project:                    Lunar Linux
Issue ID:                   62
Category:                   module
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Moonbase Version:           20060211.09
Core Tools:                 Theedge
Core Tools Version:         20060129
======================================================================
Date Submitted:             02-11-2006 09:23 UTC
Last Modified:              02-24-2006 15:57 UTC
======================================================================
Summary:                    dsniff doesnt compile with libnet-1.1
Description: 
libnet in moonbase: 1.1
libnet needed by dsniff to compile: 1.0
======================================================================

----------------------------------------------------------------------
 dveatch - 02-24-06 01:31 
----------------------------------------------------------------------
Since you did not provide the compile log I will assume you are getting
this error;

gcc -O2 -march=athlon64 -mmmx -msse -msse2 -m3dnow -mfpmath=sse,387
-D_BSD_SOURCE -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD
-DHAVE_NET_ETHERNET_H -DDSNIFF_LIBDIR=\"/usr/lib/\" -I. -I/usr/include
-I/usr/include -I/usr/include -I/usr/include -I/usr/include
-I/usr/X11R6/include -I./missing -c ./arpspoof.c
./arpspoof.c: In function `arp_send':
./arpspoof.c:51: warning: passing arg 1 of `libnet_get_hwaddr' from
incompatible pointer type
./arpspoof.c:51: error: too many arguments to function
`libnet_get_hwaddr'
./arpspoof.c:62: warning: passing arg 6 of `libnet_build_ethernet' from
incompatible pointer type
./arpspoof.c:62: error: too few arguments to function
`libnet_build_ethernet'
./arpspoof.c:66: error: `ETH_H' undeclared (first use in this function)
./arpspoof.c:66: error: (Each undeclared identifier is reported only once
./arpspoof.c:66: error: for each function it appears in.)
./arpspoof.c:66: error: too few arguments to function `libnet_build_arp'
./arpspoof.c: In function `main':
./arpspoof.c:185: warning: assignment makes pointer from integer without a
cast
make: *** [arpspoof.o] Error 1


I have tried the current moonbase versions along with the beta versions of
dsniff and libnet in various combinations. All three have the same
arpsoof.c problem.

This looks like an upstream issue with dsniff and suggest you contact the
it's author providing them with your compile results.

----------------------------------------------------------------------
 wodkahexe - 02-24-06 06:33 
----------------------------------------------------------------------
hm, sorry, forgot about that. but this is the same error i get.
the problem seems to be libnet, not dsniff itself.
dsniff has been developed for libnet 1.0 and libnet 1.1 is incompatible
with libnet 1.0. Not dsniff's fault but libnet fault. (see
http://www.groar.org/patch/english.shtml)

----------------------------------------------------------------------
 dveatch - 02-24-06 15:56 
----------------------------------------------------------------------
Using 2.4b1-sined-2 and downgrading libnet to 1.0.tgz is no better. Get
fatal make errors on ./sshcrypto.c.

I also tried libnet-1.0.1a.tgz, libnet-1.0.1b.tar.gz, libnet-1.0.1.tgz,
libnet-1.0.2a.tar.gz, lunar/libnet-1.0.2.tgz, 1.1.3-RC-01 and
libnet-1.1.2.1.tar.gz. All caused dsniff to fail with various other
errors.

While it *might* be a problem with libnet. Reading 
http://www.groar.org/patch/english.shtml there seems to be other issues
between the dsniff and libnet folks.

I am not inclined to pursue this any further by, for example generating
our own fixes/patches. This in my view is an upstream problem and should
be resolved there.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-11-06 09:23 wodkahexe      New Issue                                    
02-11-06 09:23 wodkahexe      Moonbase Version          => 20060211.09     
02-11-06 09:23 wodkahexe      Core Tools                => Theedge         
02-11-06 09:23 wodkahexe      Core Tools Version        => 20060129        
02-24-06 01:31 dveatch        Note Added: 0000127                          
02-24-06 06:33 wodkahexe      Note Added: 0000128                          
02-24-06 15:56 dveatch        Note Added: 0000129                          
02-24-06 15:57 dveatch        Assigned To               => dveatch         
02-24-06 15:57 dveatch        Status                   new => assigned     
02-24-06 15:57 dveatch        Resolution               open => won't fix   
======================================================================