Nmap Development mailing list archives

Re: Ncrack suggestion.


From: Richard Miles <richard.k.miles () googlemail com>
Date: Sun, 28 Mar 2010 17:41:36 -0500

Hi!

My machine has BackTrack Linux running with 512 MB of ram (vmware). Below is
the output of top command before Ncrack:

Mem:    510600k total,    48224k used,   462376k free,

And during Ncrack (maybe 2 minutes before it get killed):

Mem:    510600k total,   458640k used,    51960k free

Thanks.

On Sun, Mar 28, 2010 at 5:01 PM, Fyodor <fyodor () insecure org> wrote:

On Sun, Mar 28, 2010 at 03:44:04PM -0500, Richard Miles wrote:
Hi!

I found the problem. The linux kernel is killing Ncrack because it start
to
eat so much memory, when it arrives near to 97% the linux kernel kill
Ncrack
process to keep the Linux integrity.

I confirmed it looking at top command, it start with a few memory
allocated,
but in a few minutes it start to eat, eat and eat more memory and never
release it.

Thanks for the report.  How much RAM does your machine have?  How high
did Ncrack get to before it was killed?

Cheers,
-F

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


Current thread: