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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0612240111250.20280@yvahk01.tjqt.qr>
Date:	Sun, 24 Dec 2006 01:12:35 +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


>I've set up some stuff on my box where /etc/security/limits.conf
>contains the following:
>
>@users          soft    nproc           3072
>@users          hard    nproc           4096
>
>I'm in group users, and a simple fork bomb is easily quashed by this:
>
>bluefox@...box:~$ :(){ :|:; };:
>bash: fork: Resource temporarily unavailable
>Terminated
>
>Oddly enough, trying this again and again yields the same results; but,
>I can kill the box (eventually; about 1 minute in I managed to `/exec
>killall -9 bash` from x-chat, since I couldn't get a new shell open)
>with the below:

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.


	-`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/