Nmap Development: Re: [PATCH] Experimental SCTP scan support

[Fyodor <fyodor () insecure org>]

On Sat, Jan 03, 2009 at 10:39:49AM +0000, doug () hcsw org wrote:
> On Sat, Jan 03, 2009 at 03:48:09AM -0600 or thereabouts, Kris Katterjohn wrote:
> ...
>
> For anyone not familiar with this error message, it is from a fairly
> recent addition to gcc called _FORTIFY_SOURCE. Kris observed this
> error because Ubuntu enables _FORTIFY_SOURCE=2 by default on all
> gcc compiles, unlike many other linux distros.
Sounds like a great feature!  Anyone want to make a patch so that Nmap
always uses this when available?  It would be good for security, and
may help us identify bugs which might otherwise go unnoticed (as we
saw in this case).  Ideally it would cover PCRE and OpenSSL too.  The
keys are:

o Can't have a significant performance penalty (I don't think it
  would, but it is worth a few test scans to make sure).

o Can't break the Windows compile or compilation in any other cases
  where the feature is unavailable.

o Obviously, Nmap still has to work :).

Cheers,
-F

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