|
Nmap Development
mailing list archives
Re: Errors with -sV and -PE using IPv6
From: Will Cladek <william.cladek () nrl navy mil>
Date: Mon, 14 Jan 2008 10:48:01 -0500
All,
Just tried nmap with the patch against some v6 hosts with RPC ports, and the RPC scan seems to work fine now. Thanks
for the help!
-Will
Kris Katterjohn wrote:
Fyodor wrote:
On Wed, Jan 09, 2008 at 12:49:58PM -0500, Will Cladek wrote:
After breaking out my rusty programming skills, I figured out what
was causing the seg fault with the -sV option in IPv6. It's the
following code in scan_engine.cc, starting at line 5101, and then the
same code again at 5129:
Thanks for your research! As you note, the right way to fix this is
to fix send_rpc_query() to handle IPv6 addresses. It shouldn't be too
hard, since it isn't generating raw packets and Nmap already has the
code to handle TCP and UDP communication over IPv6. Anyone want to
give it a try? We support IPv6 for the rest of version detection, so
we should do so for RPC scan, unless there is some major difficulty
with doing so.
Hey Fyodor!
I've attached a patch which adds this. I must warn that, while the IPv6
code I've added has compiled fine for me, I haven't tested that the
actual connect() and things work properly for IPv6 as I don't have a
portmap that supports it.
I /have/ tested it using TCP and UDP over IPv4 on my system, and it
gives the same results as before the patch. Since the code is pretty
much the same between IPv4 and IPv6, I'm betting that it will work fine
as well.
I'd appreciate anybody testing this (IPv4 and IPv6) and letting me know
how it goes.
Cheers,
-F
Thanks,
Kris Katterjohn
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
By Date
By Thread
Current thread:
|