Nmap Development mailing list archives
Re: nmap-5.20 on x86_64 Segmentation fault
From: Kris Katterjohn <katterjohn () gmail com>
Date: Mon, 25 Jan 2010 20:46:09 -0600
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/25/2010 08:27 PM, Brandon Enright wrote:
On Mon, 25 Jan 2010 07:37:32 -0600 Kris Katterjohn <katterjohn () gmail com> wrote: [...snip...]Socket troubles: Address family not supported by protocol nmap: nsock_core.c:1163: nsp_add_event: Assertion `nse->iod->sd= 0' failed. AbortIndeed, Nsock doesn't do IPv6 yet.Odds are I'm misunderstanding the issue (since I didn't receive Gunnar's email quoted here) or I'm not following this correctly, but what do you mean nsock doesn't do IPv6? Perhaps the assertion failure above was triggered with code utilizing a special part of nsock which doesn't support IPv6 yet, but I just wanted clarification here :) I know IPv6 is supported in Ncat via nsock, and surely NSE and version detection support IPv6 with it too.BrandonThanks, Kris KatterjohnHey Kris, sorry it took me all day to find the time to dig into this.
Hey Brandon. No worries: I was only almost late for class trying to push this out, so we're all good ;) Eh, who am I kidding? It was just Linear Algebra so feel free to have me respond another morning :P
So, specifically for Gunnar's issue, we can't read IPv6 addresses longer than 16 characters in /etc/resolv.conf without smashing the stack. We need to fix this but rather than hardcode a buffer of 128, David had some better ideas. I'm happy to code them up but I can't remember the name of the IPv6 address max string length constant he pointed out to me...
INET6_ADDRSTRLEN in netinet/in.h. And actually a quick grep yielded this defined in Target.h as well. Not sure why that's not in tcpip.h with the IPv4 one also defined there.
Brandon
Cheers, Kris Katterjohn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJLXldxAAoJEEQxgFs5kUfuELYP/2mMEAHuERaBUN24l3hmgSDO whcAnFS5m0m5aXvxcfg2g6Xg0xVv0bwRqJa631v5qkYIS/eTPNuPoEy4BT6/GD0c yL+Xl9FZ9yBUogo4zbKevT4F1GeMF4rY9XQ+7aEA41KIqbtmBQ5fo05xCpzmC6Yl efky00JW+5iLs+2C8+jn5YOTaogOW5KdAn8W5NLyYR4FrJFNPJxoxhWDebYc9l/c XRqidZD/zz1v3OnySM4k77h2CXoFD0Xb3N3vRTo03Es9mqlO7nqBf+TtLgOrTWfr Ni2kDraP1FEqMxYUtGrSnbYQ6iczePSM7TaI2JHul6BdLnKYK/k07sIoDdIKquei t+q0Mc2vLGmV7Zya5d+gaV6rI88YX8pY1p9j48tpg6WaZpE9JCdbf5fM93pxSCyA 4cGDV84Dk+xytBXmwl+dszw77MW7rPiHqfiNUdSHYTt1A3W4vLY5KqBFTGLTEQU2 raiYECzbtj2o9LsU1irCEpDAJVUda1WulkCRV6vlrZqAUDXQRzWWM4SZF7QZdEH2 P7lqjwhbSlsAjx9L2uFrY9i5WjT2fagdZo0i4fYIlc55j0NgGnmXy0jKsilZL0q+ 7Td6VQIV/C5KtCkYFG2Q4Z42qEmtK1Z4cZXa2PWTPq29CESDfpzlHeQeCNRnkny2 k4M6OXTg0OFRLfMusD7J =X588 -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- nmap-5.20 on x86_64 Segmentation fault Gunnar Lindberg (Jan 23)
- Re: nmap-5.20 on x86_64 Segmentation fault Brandon Enright (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Brandon Enright (Jan 24)
- Re: nmap-5.20 on x86_64 Segmentation fault Gunnar Lindberg (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Gunnar Lindberg (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Brandon Enright (Jan 24)
- Re: nmap-5.20 on x86_64 Segmentation fault Kris Katterjohn (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Brandon Enright (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Kris Katterjohn (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Gunnar Lindberg (Jan 26)
- Re: nmap-5.20 on x86_64 Segmentation fault Kris Katterjohn (Jan 26)
- Re: nmap-5.20 on x86_64 Segmentation fault David Fifield (Jan 27)
- Re: nmap-5.20 on x86_64 Segmentation fault Brandon Enright (Jan 24)
- Re: nmap-5.20 on x86_64 Segmentation fault Brandon Enright (Jan 25)
- Re: nmap-5.20 on x86_64 Segmentation fault Gunnar Lindberg (Jan 25)