Nmap Development mailing list archives
Re: nmap stack overflow in output subsystem
From: Ron <ron () skullsecurity net>
Date: Mon, 02 Jul 2012 17:01:48 -0700
I was running into this issue, but was having trouble reproducing it. This patch seems too have fixed it.
Ron On 7/2/2012 3:39 PM, Henri Doreau wrote:
Small update: even though my previous patch fixes the symptoms it doesn't actually remove the call loop between fatal() and log_vwrite(). This second patch, attached, replaces the one I sent earlier. It calls abort() instead of fatal() on unknown event log types, which I think is OK in this case. Any thought? _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
_______________________________________________ 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 stack overflow in output subsystem Henri Doreau (Jul 02)
- Re: nmap stack overflow in output subsystem Henri Doreau (Jul 02)
- Re: nmap stack overflow in output subsystem Ron (Jul 02)
- Re: nmap stack overflow in output subsystem David Fifield (Jul 03)
- Re: nmap stack overflow in output subsystem Henri Doreau (Jul 03)
- Re: nmap stack overflow in output subsystem Daniel Miller (Jul 03)
- Re: nmap stack overflow in output subsystem David Fifield (Jul 03)
- Re: nmap stack overflow in output subsystem Daniel Miller (Jul 03)
- Re: nmap stack overflow in output subsystem Henri Doreau (Jul 02)