Re: valgrind complains on uninitialised bytes

[Vasily Kulikov <segoon () openwall com>]

On Tue, Aug 13, 2013 at 08:25 -0700, David Fifield wrote:
> On Tue, Aug 13, 2013 at 12:23:15PM +0400, Vasily Kulikov wrote:
> > With --with-libpcap=included the bug is gone.  Is it a bug in Ubuntu's
> > version of libpcap or in the nmap's way of libpcap's usage?
>
> I think it is neither; rather it is that Valgrind doesn't know the way
> setsockopt is used in this case. Nmap's version of libpcap might have
> been patched to make the warning go away.
>
> https://github.com/mcr/libpcap/issues/25
> http://seclists.org/nmap-dev/2010/q3/796
> https://bugs.kde.org/show_bug.cgi?id=318203

Oh, this is a known issue.  I should have googled first, sorry for the
noise.

-- 
Vasily Kulikov
http://www.openwall.com - bringing security into open computing environments
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/