LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: "Anand Jahagirdar" <anandjigar@gmail.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Fork Bombing Attack
Date: Fri, 18 May 2007 16:19:56 +0300	[thread overview]
Message-ID: <1865922a0705180619g2a997c2ch5d13be3e023630e0@mail.gmail.com> (raw)
In-Reply-To: <25ae38200705180413s741cac1bw9fe0dc57cecc2a91@mail.gmail.com>

On 5/18/07, Anand Jahagirdar <anandjigar@gmail.com> wrote:
> Hello All
>            I tried to execute a program which creates 8152 process.(
> i=0; while( i<14) i++ fork(); )  with ulimit 8200. This program
> created 8152 processes and then stopped and came back to command
> prompt. this proves that my machine do have sufficient resources to
> create 8000 processes.
>
>            I found one more interesting thing on the same machine
> having FC6 distribution and Linux Kernel 2.6.18. i have set "ulimit -u
> 100". after setting this limit i tried to execute fork bombing program
> with guest account. after executing it
>
> expected result:-  guest uesr should not able to fork another single
> process when it reaches to 100 processes count.
>
> actual result :-  kernel allow me to create another processes without
> giving error. due to this i tried to execute same fork bombing program
> on another terminal with guest account and this fork bombing attack
> killed the box completely and machine needed reboot.
>

I think if you want resource limiting per _UID_ (and not per _process_
as you did), you should use PAM module pam_limits.so. You can edit
those limits using the file /etc/security/limits.conf

Regards,
-- 
Ahmed S. Darwish
http://darwish-07.blogspot.com

  parent reply	other threads:[~2007-05-18 13:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 14:45 Anand Jahagirdar
2007-05-17 15:01 ` Valdis.Kletnieks
2007-05-18 11:13   ` Anand Jahagirdar
2007-05-18 13:07     ` Michael Tokarev
2007-05-18 13:19     ` Ahmed S. Darwish [this message]
2007-05-18 17:22       ` Anand Jahagirdar
2007-05-18 17:49         ` Valdis.Kletnieks
2007-05-18 21:21         ` Krzysztof Halasa
2007-05-18 22:40         ` Bernd Eckenfels
2007-05-22 21:52     ` Mark Lord
  -- strict thread matches above, loose matches on Subject: below --
2007-05-17  7:25 Fork bombing Attack Anand Jahagirdar
2007-05-17  7:39 ` Marat Buharov
2007-05-17  9:07 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1865922a0705180619g2a997c2ch5d13be3e023630e0@mail.gmail.com \
    --to=darwish.07@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=anandjigar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Fork Bombing Attack' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox