From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Fork Bombing Attack
Organization: Private Site running Debian GNU/Linux
In-Reply-To: <25ae38200705181022l35e0b364p98fc39e5739612b@mail.gmail.com>
User-Agent: tin/1.7.8-20050315 ("Scalpay") (UNIX) (Linux/2.6.13.4 (i686))
Message-Id: <E1HpB7Z-000339-00@calista.eckenfels.net>
Date: Sat, 19 May 2007 00:40:25 +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 882
Lines: 22

In article <25ae38200705181022l35e0b364p98fc39e5739612b@mail.gmail.com> you wrote:
>           I found one more interesting thing related with fork
> bombing attack. i have set following in /etc/security/limits.conf file
> 
>     #@root    hard  nproc  3000
>     #@anand hard  nproc  500

The # is a comment character. So those lines are not used.

BTW: the @ means group, you really want that? BTW2: you need to log out/in
and the session leader must actually be PAM regulated (i.e. not for daemons)

So it is good to check "ulimit -n" in the shell where you want to try the
forbomb. If it is below 100 you should be safe.

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