The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: toresbe@ifi.uio.no (Tore Sinding Bekkedal)
Subject: [pups] User Mode DoS Attacks (was Re: Issues of AUUGN)
Date: Thu, 05 Oct 2006 16:51:02 +0200	[thread overview]
Message-ID: <1160059862.4423.94.camel@localhost.localdomain> (raw)
In-Reply-To: <E183486F-6903-48DA-BBC2-D35A498B86A6@uwlax.edu>

(oops, sent it off-list - sorry, Milo!)

On Thu, 2006-10-05 at 08:46 -0500, Milo Velimirovic wrote:
> > But you'd need kernel mode for that; this is a DoS attack (one of the
> > first?) launched by a user.
> 
> The userland DoS I remember:
> 
> main() {
> 	while(1)
> 		fork();
> }
> 
> And in fact I tried it once on the 11/45 I had access to. Not pretty.  
> It can be made less disastrous by judicious addition of a wait(); call.
> 
> --Milo, wondering how contemporary UNIX will deal with such  
> pathological behavior....

Speaking for Linux, quite badly, though there are some patches that
allow you to limit forks per user. There's even a bash version,
":(){ :|:& };:", which will infinitely fork off bash processes. (It
defines a function calling itself in the background, and then
immediately launches it)

The max number of processes is not so much a problem as the fact that
they are all draining the system resources. Besides, one is likely to
run out of memory before one hits the max process number in Linux
anyway.

- Tore Sinding Bekkedal




      parent reply	other threads:[~2006-10-05 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1160013601.40099.pups@minnie.tuhs.org>
2006-10-05 13:46 ` Milo Velimirovic
2006-10-05 14:33   ` Bill Gunshannon
2006-10-05 14:44     ` Johnny Billquist
2006-10-05 14:51   ` Tore Sinding Bekkedal [this message]

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=1160059862.4423.94.camel@localhost.localdomain \
    --to=toresbe@ifi.uio.no \
    /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;
as well as URLs for NNTP newsgroup(s).