mailing list archives
James Rogers - Status Report #7 of 17
From: James Rogers <jamesmrogers () gmail com>
Date: Mon, 11 Jun 2012 17:30:14 -0400
Checked out the nmap-npingchanges development folder and am currently
running clang against it.
Read RFC 793 Transmission control protocol.
Read RFC 768 UDP.
Read several chapters out of TCP Illustrated by Stevens.
Read up on several sites about TCP handshaking.
Added a sequence number to the ack packet to see if that makes a
difference in the spurious port closed bug.
Someone fixed a memory leak bug that clang pointed out, so a few of
the things clang pointed out are real and serious.
1) Reproduce the spurious closed port issue, research it to figure out
why it is happening, think up and try potential solutions to see if
they fix it.
2) Finish running clang on Nping dev branch, read the report, research
each potential issue and categorize into sections like "definitely not
a problem", "probably a problem", and "definitely seems to be a
problem", by area, with notes justifying why they are in each.
3) For the ones which are definitely an issue, would be great to
write a patch where you can, especially for the ones where the patch
is rather straightforward and simple and the issue is clear
4) Same as #2 and #3, but for /nmap trunk
Finished the quarter last Wednesday, can now devote my full energies to nmap.
Graduated from 2 year school last Saturday, Liberal Arts Transfer and
General Science Degrees.
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/
- James Rogers - Status Report #7 of 17 James Rogers (Jun 11)