linux-kernel - Re: evading ulimits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0612241120370.16427@yvahk01.tjqt.qr>
Date:	Sun, 24 Dec 2006 11:21:05 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	John Richard Moser <nigelenki@...cast.net>
cc:	linux-kernel@...r.kernel.org
Subject: Re: evading ulimits


On Dec 23 2006 19:42, John Richard Moser wrote:
>Jan Engelhardt wrote:
>> 
>> Note that trying to kill all shells is a race between killing them all first
>> and them spawning new ones everytime. To stop fork bombs, use killall -STOP
>> first, then kill them.
>
>Yes I know; the point, though, is that they should die automatically
>when the process count hits 4096.  They do with the first fork bomb;
>they keep growing with the second, well past what they should.

They don't just all die when you hit 4096. If you do nothing, 4096 +/- n will
stay around.


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/