<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nmap Development</title>
    <link>http://seclists.org/#nmap-dev</link>
    <atom:link href="http://seclists.org/rss/nmap-dev.rss" rel="self" type="application/rss+xml" />
    <language>en-us</language>
    <description>Unmoderated technical development forum for debating ideas, patches, and suggestions regarding proposed changes to &lt;A HREF=&quot;http://nmap.org&quot;&gt;Nmap&lt;/A&gt; and related projects.</description>
    <pubDate>Sat, 07 Nov 2009 21:15:08 GMT</pubDate>
    <lastBuildDate>Sat, 07 Nov 2009 21:15:08 GMT</lastBuildDate>
<!-- MHonArc v2.6.16 -->

 

  <item>
    <title>Re: OS X 10.6 diagnosis: pcap timeout and bpf device access</title>
    <link>http://seclists.org/nmap-dev/2009/q4/280</link>
    <description>&lt;p&gt;Posted by David Fifield on Nov 07&lt;/p&gt;I think it's because the release I made on 10.5 was compiled as a 32-bit&lt;br&gt;
executable, and the default compiler target on 10.6 is 64-bit, but I&lt;br&gt;
haven't tested that yet. We could, of course, build the next release as&lt;br&gt;
32-bit, but that doesn't help the people who build from source unless we&lt;br&gt;
make it automatic in the build system.&lt;br&gt;
&lt;br&gt;
For what it's worth, I ran a copy of Nmap that I had built on 10.5 and&lt;br&gt;
still had installed after upgrading to 10.6. It...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 21:00:04 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/280</guid>
  </item>
  <item>
    <title>Re: OS X 10.6 diagnosis: pcap timeout and bpf device access</title>
    <link>http://seclists.org/nmap-dev/2009/q4/279</link>
    <description>&lt;p&gt;Posted by Walt Scrivens on Nov 07&lt;/p&gt;David,&lt;br&gt;
Thanks for sticking with this.  You've done an impressive bit of  &lt;br&gt;
analysis work.  Your explanation is so good that even I begin to  &lt;br&gt;
understand what's going wrong, although I suppose the chances of apple  &lt;br&gt;
ever doing anything about it are slim to none.&lt;br&gt;
&lt;br&gt;
Since the problem doesn't happen in the released version 5, the  &lt;br&gt;
problems you've uncovered are specific to 5.05BETA-1.  Do we know why  &lt;br&gt;
those changes were made, and what the impact of...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 19:57:34 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/279</guid>
  </item>
  <item>
    <title>Re: Simple script: random (garbage) fuzzer</title>
    <link>http://seclists.org/nmap-dev/2009/q4/278</link>
    <description>&lt;p&gt;Posted by Jon Kibler on Nov 07&lt;/p&gt;Fyodor wrote:&lt;br&gt;
&lt;br&gt;
Re: Use case for this script?&lt;br&gt;
&lt;br&gt;
I have not had a chance to look at this NSE script. However, random garbage&lt;br&gt;
generators are a VERY useful testing tool, especially against embedded systems&lt;br&gt;
(printers, VoIP phones, environmental sensors, etc.) and real-time systems&lt;br&gt;
(SCADA, PLCs, DCS, security, HVAC, etc.). They very rapidly identify brittle IP&lt;br&gt;
stacks and how well systems handle unexpected traffic.&lt;br&gt;
&lt;br&gt;
I regularly use custom protocol...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 18:06:53 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/278</guid>
  </item>
  <item>
    <title>OS X 10.6 diagnosis: pcap timeout and bpf device access</title>
    <link>http://seclists.org/nmap-dev/2009/q4/277</link>
    <description>&lt;p&gt;Posted by David Fifield on Nov 07&lt;/p&gt;I have been looking into this problem, and I think I have found the&lt;br&gt;
cause, or rather causes, both of which appear to be Apple bugs. The&lt;br&gt;
first is that setting timeouts for read events doesn't work unless the&lt;br&gt;
timeout is at least 1000 milliseconds. The second is that opening a&lt;br&gt;
/dev/bpf? device in O_WRONLY mode and binding it to an interface causes&lt;br&gt;
all other listeners on the interface to see only outgoing traffic. I&lt;br&gt;
don't know of a nice quick fix for...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 18:01:53 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/277</guid>
  </item>
  <item>
    <title>exclude targets</title>
    <link>http://seclists.org/nmap-dev/2009/q4/276</link>
    <description>&lt;p&gt;Posted by Si Stransky on Nov 07&lt;/p&gt;My salutations to all nmap followers,&lt;br&gt;
&lt;br&gt;
I have something going wrong with certain sorts of exclude targets..&lt;br&gt;
see for example&lt;br&gt;
&lt;br&gt;
$ nmap -sL -n  --exclude 10.0-253.0.1 10.250-255.0.22&lt;br&gt;
..&lt;br&gt;
nmap: TargetGroup.cc:459: int&lt;br&gt;
TargetGroup::get_next_host(sockaddr_storage*, size_t*): Assertion&lt;br&gt;
`ipsleft == 1' failed.&lt;br&gt;
Aborted&lt;br&gt;
&lt;br&gt;
$ nmap -sL -n -q --exclude 10.10.250-255.22 10.10.250-255.0-255&lt;br&gt;
..&lt;br&gt;
pine: TargetGroup.cc:459: int...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 13:34:52 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/276</guid>
  </item>
  <item>
    <title>Re: Simple script: random (garbage) fuzzer</title>
    <link>http://seclists.org/nmap-dev/2009/q4/275</link>
    <description>&lt;p&gt;Posted by Ron on Nov 07&lt;/p&gt;Fyodor wrote:&lt;br&gt;
&lt;br&gt;
No, I'm doing a class right now and the instructor mentioned it. His&lt;br&gt;
case was primarily finding low-hanging fruit services on certain systems.&lt;br&gt;
&lt;br&gt;
It might be need to write fuzzers for specific protocols, too. HTTP&lt;br&gt;
fuzzer, SMB fuzzer, etc etc. That's something I hadn't really thought of&lt;br&gt;
using NSE for before.&lt;br&gt;
&lt;br&gt;
Sure, any suggestions on how long it should go for?&lt;br&gt;
&lt;br&gt;
Most services do terminate the connection pretty fast when they receive...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 12:24:21 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/275</guid>
  </item>
  <item>
    <title>Zenmap fails to start.</title>
    <link>http://seclists.org/nmap-dev/2009/q4/274</link>
    <description>&lt;p&gt;Posted by AFH Security on Nov 07&lt;/p&gt;Hey guys,&lt;br&gt;
&lt;br&gt;
Running Ubuntu 9.10 Karmic Koala, on an amd64 system arch.&lt;br&gt;
When I try to run zenmap (I wanted to see the new filter list button &lt;br&gt;
that was mentioned in the change log) I get the following error.&lt;br&gt;
&lt;br&gt;
&amp;quot;[Errno 2] No such file or directory: '/usr/share/zenmap/config'&amp;quot;&lt;br&gt;
&lt;br&gt;
I searched my comp, and the zenmap dir is located at &lt;br&gt;
&amp;quot;/usr/local/share/zenmap&amp;quot;&lt;br&gt;
Any idea on what I'm doing wrong?&lt;br&gt;
&lt;br&gt;
The steps I took to compile were the...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 09:33:37 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/274</guid>
  </item>
  <item>
    <title>Support for IPv6 name servers in nmap</title>
    <link>http://seclists.org/nmap-dev/2009/q4/273</link>
    <description>&lt;p&gt;Posted by Ankur Nandwani on Nov 06&lt;/p&gt;Hey Guys,&lt;br&gt;
&lt;br&gt;
I just wrote a patch for Nmap's parallel DNS resolver which allows it&lt;br&gt;
to make use of IPv6 name servers. David has committed the patch in&lt;br&gt;
r16016. Please test it and let me know if there are any issues.&lt;br&gt;
&lt;br&gt;
Thanks&lt;br&gt;
Ankur&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 07:25:30 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/273</guid>
  </item>
  <item>
    <title>Re: Simple script: random (garbage) fuzzer</title>
    <link>http://seclists.org/nmap-dev/2009/q4/272</link>
    <description>&lt;p&gt;Posted by Fyodor on Nov 06&lt;/p&gt;Nice.  Did they request it on a public forum somewhere that you can&lt;br&gt;
link to?  It would be interesting to know more about the use case they&lt;br&gt;
have in mind.&lt;br&gt;
&lt;br&gt;
Maybe it should include a stopafter limit by default?  That way it&lt;br&gt;
doesn't go forever for people who acidentally specify it (perhaps&lt;br&gt;
among other scripts) without specifying the stopafter arg.&lt;br&gt;
&lt;br&gt;
Also, you might want to make this output line more clear:&lt;br&gt;
return false, string.format(&amp;quot;Finished...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 07:16:22 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/272</guid>
  </item>
  <item>
    <title>Re: Ron/fuzz-garbage script</title>
    <link>http://seclists.org/nmap-dev/2009/q4/271</link>
    <description>&lt;p&gt;Posted by Ron on Nov 06&lt;/p&gt;Hi mike,&lt;br&gt;
&lt;br&gt;
You're right about the chunksize -- the way I designed it, it only sends&lt;br&gt;
in 'chunksize' blocks, so the 'stopafter' value is rounded up (I put&lt;br&gt;
that in the NSEDoc at the top). It's the cleanest way to do it, I think.&lt;br&gt;
&lt;br&gt;
Can you link to where you reported that error? I don't remember anything&lt;br&gt;
about it, but it may be from before my time (or in a thread I didn't read)&lt;br&gt;
&lt;br&gt;
Thanks!&lt;br&gt;
Ron&lt;br&gt;
&lt;br&gt;
mike wrote:&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 03:13:03 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/271</guid>
  </item>
  <item>
    <title>Ron/fuzz-garbage script</title>
    <link>http://seclists.org/nmap-dev/2009/q4/270</link>
    <description>&lt;p&gt;Posted by mike on Nov 06&lt;/p&gt;Ron&lt;br&gt;
&lt;br&gt;
not sure if this is a windows thing or not. i noticed the output after i tested it and i set the args value for &lt;br&gt;
&amp;quot;stopafter&amp;quot; to just 10 bytes. the output from nmap reports this as &amp;quot;10 bytes sent&amp;quot; howver i noticed that what was sent &lt;br&gt;
to the socket in testing was the 1024 bytes default value. seting the chunksize is apparently the only way i can &lt;br&gt;
control the bytes to be the exact value that nmap reports back as what was...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 01:04:01 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/270</guid>
  </item>
  <item>
    <title>Re: man page translations</title>
    <link>http://seclists.org/nmap-dev/2009/q4/269</link>
    <description>&lt;p&gt;Posted by Fyodor on Nov 06&lt;/p&gt;I'm all for that!&lt;br&gt;
&lt;br&gt;
That concerned me at first because most people will want at most 1 or&lt;br&gt;
2 languages, and we already have 16 with more coming.  But the&lt;br&gt;
instructions later in your email may be the best way for such people&lt;br&gt;
to proceed.&lt;br&gt;
&lt;br&gt;
I have those directories, but even the largest of them is less than&lt;br&gt;
10% the size of my English man pages.&lt;br&gt;
&lt;br&gt;
This sounds like a good way for people who don't want the extra man&lt;br&gt;
pages to deal with it.  As you note, it...&lt;br&gt;</description>
    <pubDate>Sat, 07 Nov 2009 00:15:43 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/269</guid>
  </item>


  <item>
    <title>Implementation sketch for Ncat caretaker processes</title>
    <link>http://seclists.org/nmap-dev/2009/q4/268</link>
    <description>&lt;p&gt;Posted by David Fifield on Nov 06&lt;/p&gt;Look at the netrun function in ncat_posix.c. It forks to create a new&lt;br&gt;
process, then calls netexec. netexec reassigns some file descriptors,&lt;br&gt;
then runs execl to run a new process with the changed descriptors. When&lt;br&gt;
the new process reads and writes stdin and stdout, it is really reading&lt;br&gt;
and writing the socket.&lt;br&gt;
&lt;br&gt;
What I was thinking of is that netexec can first create a pair of pipes&lt;br&gt;
(...&lt;br&gt;</description>
    <pubDate>Fri, 06 Nov 2009 22:47:40 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/268</guid>
  </item>
  <item>
    <title>Re: nmap XML output - host latency</title>
    <link>http://seclists.org/nmap-dev/2009/q4/267</link>
    <description>&lt;p&gt;Posted by David Fifield on Nov 06&lt;/p&gt;We already have an element for latency, but it seems it is not written&lt;br&gt;
for ping scans. &amp;quot;nmap -oX - -F scanme.nmap.org&amp;quot; prints&lt;br&gt;
&lt;br&gt;
&amp;lt;times srtt=&amp;quot;68616&amp;quot; rttvar=&amp;quot;20892&amp;quot; to=&amp;quot;152184&amp;quot; /&amp;gt;&lt;br&gt;
&lt;br&gt;
but &amp;quot;nmap -oX - -sP scanme.nmap.org&amp;quot; doesn't print it. I think this is&lt;br&gt;
just an oversight because there are two separate places where host&lt;br&gt;
output can be written depending on whether anything happens past a ping&lt;br&gt;
scan....&lt;br&gt;</description>
    <pubDate>Fri, 06 Nov 2009 21:02:35 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/267</guid>
  </item>
  <item>
    <title>Re: Ron/fuzz-garbage script</title>
    <link>http://seclists.org/nmap-dev/2009/q4/266</link>
    <description>&lt;p&gt;Posted by Ron on Nov 06&lt;/p&gt;Hi Mike,&lt;br&gt;
&lt;br&gt;
It shouldn't freeze Nmap, but it could be an issue with how the Windows&lt;br&gt;
version of Nmap handles sockets. All it's doing it looping and sending&lt;br&gt;
data. My solution would be to not run Nmap on Windows, but that's just me ;)&lt;br&gt;
&lt;br&gt;
As for different chunksizes, the functionality already exists. There are&lt;br&gt;
two script-args, one for the total amount of data to send (default:&lt;br&gt;
unlimited), and one for the size of the chunks (default: 1024).&lt;br&gt;
&lt;br&gt;
Ron&lt;br&gt;
&lt;br&gt;
mike...&lt;br&gt;</description>
    <pubDate>Fri, 06 Nov 2009 19:59:38 GMT</pubDate>
    <guid isPermaLink="true">http://seclists.org/nmap-dev/2009/q4/266</guid>
  </item>

 

<!-- MHonArc v2.6.16 -->
  </channel>
</rss>
