Nmap Development mailing list archives
Re: Potential bug in nmap 4.21ALPHA4 (and before)
From: Fyodor <fyodor () insecure org>
Date: Wed, 16 May 2007 17:33:32 -0700
On Wed, May 16, 2007 at 11:19:12PM +0200, Sebastian Wolfgarten wrote:
And here is the problem: Which option does actually suck (send_closedudp_probe: One or more of your parameters suck!)? Why do I get these messages when to me the command-line call above looks quite alright, doesn't it?
Thanks for the report, Sebastian. This is definitely an Nmap bug related to a combination of scanning port zero and OS scan, but after looking into the code, I think this only affects the old OS detection system. Since I hope to get rid of that 1st generation system completely, it probably isn't worth fixing and testing. Though if someone wants to, I'd certainly accept a patch. And if you are able to reproduce this with -O2 (sencond generation system), please post the log. Thanks! -Fyodor _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Potential bug in nmap 4.21ALPHA4 (and before) Sebastian Wolfgarten (May 16)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Fyodor (May 16)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Kris Katterjohn (May 16)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Sebastian Wolfgarten (May 17)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Kris Katterjohn (May 16)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Sebastian Wolfgarten (May 17)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Kris Katterjohn (May 16)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Fyodor (May 16)
- Re: Potential bug in nmap 4.21ALPHA4 (and before) Sebastian Wolfgarten (May 17)