Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Development: Re: How is whois.nse coming along?

Re: How is whois.nse coming along?

From: jah <jah_at_zadkiel.plus.com>
Date: Tue, 01 Jul 2008 21:45:43 +0100

On 30/06/2008 05:06, Patrick Donnelly wrote:
> I haven't merged any of my nse_main changes with the main branch.
> Threads should still have an undefined execution order in my branch,
> is that where you are testing. I get the impression that "merge of
> Patrick's branch" implies you are testing in /nmap?
Yes, I was talking about the behaviour of threads in /nmap (rather than
in your branch) after the commit (r8377) you mentioned in [1] - which,
as you rightly say, wasn't a merge at all! I did much of the mutex
stuff for whois.nse in your branch (I think I'd checked-out r8260) where
I noticed and subsequently worked around the undefined thread execution
order. Whilst the workaround isn't currently necessary under /nmap, I'm
glad I was able to add it because the ordered presentation of results of
whois.nse was, until then, entirely dependent on ordered thread
execution and I'd not considered what would happen if that behaviour
changed.

Cheers,

jah

[1] - http://seclists.org/nmap-dev/2008/q2/0796.html

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Jul 01 2008

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos