Nmap Development mailing list archives

Re: Ncat without IPv6 and rpl_malloc


From: bensonk () acm wwu edu
Date: Sun, 21 Dec 2008 02:02:23 -0800

I'm hoping to eventually get it running on my T-Mobile G1, which is a
device running the Google / Open Handset Alliance operating system known
as Android.  It's basically a stripped down linux install on a 500 MHz
processor.  The catch is that I don't have root, and I'll have to find a
cross compiler for the device, and I'll be stuck with non-raw socket
access.  :-(

Benson

On Fri, Dec 19, 2008 at 09:43:20PM +0100, Dirk Loss wrote:
Kris Katterjohn wrote:
On 12/19/2008 10:43 AM, Dirk Loss wrote:
What would be the recommended way to disable IPv6 (which my device
doesn't support) and rpl_malloc (which lead to a compilation
error)?
"configure --disable-ipv6" should do the trick for IPv6,

Thanks, that worked.

try running autoconf and building configure yourself to fix the
rpl_malloc problem.

This turned out to be a cross-compilation issue. I've found the following 
workaround [1]:

 $ export ac_cv_func_malloc_0_nonnull=yes
 $ ./configure

Moreover I had to run Nmap's ./configure script once before calling Ncats 
configure script.

With these compilation tweaks and no patches to Ncat or Nmap themselves I 
now can run Ncat on my little Yoggie appliance. I haven't tested SSL yet, 
but basic listening, connecting and brokering works nicely. :-)
And Nmap (including NSE) works as well.

Maybe we could make a poll out of that: What is the (physically) smallest 
device you have ever managed to run Nmap on? :-)

Regards
Dirk

[1] http://wiki.buici.com/wiki/Autoconf_and_RPL_MALLOC

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

Attachment: _bin
Description:


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

Current thread: