mailing list archives
Re: Want to work on updating libpcap included in nmap
From: Jay Bosamiya <jaybosamiya () gmail com>
Date: Mon, 10 Feb 2014 19:18:15 +0530
I understand that the diffs are much larger, but if I ignore the diffs in
libpcap/NMAP_MODIFICATIONS, how will i know even which direction to move in
to make the update?
Does it make more sense if I only take into consideration the (helpful)
titles given to the diffs, and then work on the patches? Will this be
Also, how will I know when the patches I've made are exactly what is
required for nmap? Can I run a set of tests etc.?
I tried looking for answers to these questions in multiple places but
couldn't find any. Is there any place where there is something like a FAQ
On Mon, Feb 10, 2014 at 4:16 PM, Gisle Vanem <gvanem () yahoo no> wrote:
"Jay Bosamiya" <jaybosamiya () gmail com> wrote:
In regards to my previous mail (about working on libpcap), the given
patches do NOT work directly. However, I can rewrite them to give same
functionality and make them work.
You should ignore the diffs in libpcap/NMAP_MODIFICATIONS and take
a look at the official libpcap git-repo  itself. Then you'll see the
are much larger. A simple check done here now (run diff from nmap's base):
diff -r -u3 libpcap g:\MingW32\src\inet\nmap\libpcap | wc -n
29004 << !! But this includes the generated Yacc/Lex files.
Anyway, good luck.
Sent through the dev mailing list
Archived at http://seclists.org/nmap-dev/