mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Anand Jahagirdar" <anandjigar@gmail.com>
Cc: "Ahmed S. Darwish" <darwish.07@gmail.com>,
	"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	linux-kernel@vger.kernel.org,
	"Coywolf Qi Hunt" <coywolf@sosdg.org>
Subject: Re: Fork Bombing Attack
Date: Fri, 18 May 2007 23:21:49 +0200	[thread overview]
Message-ID: <m31whdg74i.fsf@maximus.localdomain> (raw)
In-Reply-To: <25ae38200705181022l35e0b364p98fc39e5739612b@mail.gmail.com> (Anand Jahagirdar's message of "Fri, 18 May 2007 22:52:15 +0530")

"Anand Jahagirdar" <anandjigar@gmail.com> writes:

> ulimit are by default  set to some value for all users.. root, guest.
> on my machine with FC4 distribution when i typed command "ulimit -u"
> it gave me output as 3055 and another machine having FC6 distribution
> output is 8050. when root or any other user changes ulimit by typing
> "ulimit -u value",.ulimit value is changed for that session and not
> permantely. actually ulimit should help to prevent fork bombing attack
> but it wont and fork bombing attack still take down the machine having
> latest linux distributions.

how about:
$ ulimit -u 100
$ for f in `seq 1 500`; do (sleep 100&); done

(on another terminal)
$ ps xa|grep 'sleep 100' |wc -l

mine prints 93.
-- 
Krzysztof Halasa

  parent reply	other threads:[~2007-05-18 21:21 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
2007-05-18 17:22       ` Anand Jahagirdar
2007-05-18 17:49         ` Valdis.Kletnieks
2007-05-18 21:21         ` Krzysztof Halasa [this message]
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=m31whdg74i.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=anandjigar@gmail.com \
    --cc=coywolf@sosdg.org \
    --cc=darwish.07@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®