From: Peter Zijlstra <peterz@infradead.org>
To: Dane Mutters <dmutters@gmail.com>
Cc: Martin Olsson <mnemo@minimum.se>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ubuntu Devel Discuss <ubuntu-devel-discuss@lists.ubuntu.com>,
linux-kernel@vger.kernel.org
Subject: Re: Is it possible to give the user the option to cancel forkbombs?
Date: Sat, 17 Nov 2007 08:44:41 +0100 [thread overview]
Message-ID: <1195285481.3059.12.camel@twins> (raw)
In-Reply-To: <1195281942.15929.5.camel@Orchestrator>
On Fri, 2007-11-16 at 22:45 -0800, Dane Mutters wrote:
> I thought you might find this helpful. (I brought this issue up with
> the Slackware folks once, and they told me basically this.)
>
> http://wiki.craz1.homelinux.com/index.php/Linux:Security:Forkbomb
>
> I was also told that the ability to spawn such rampant forks/processes
> is controlled by default in Debian. Is this the case?
>
> Here is an LQ thread where I brought it up:
>
> http://www.linuxquestions.org/questions/linux-security-4/how-can-i-prevent-forkbombs-338560/
>
> I would like to see something done about this, with Ubuntu as popular as
> it is, even as a server in some cases. Is there a way that in the
> future, one could simply download a package or click a box or something
> and have a limit set, like the links suggest? That would make things
> just "that much" more convenient for system administrators (and might
> help them/us to remember to set these limits, too...).
If you don't know which limits to set and need a package for them, your
job title should not be system administrator.
next prev parent reply other threads:[~2007-11-17 7:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:51 Is it possible to give the user the option to cancel forkbombs? Martin Olsson
2007-11-16 21:31 ` Alan Cox
2007-11-17 7:04 ` Martin Olsson
2007-11-16 23:46 ` Alan Cox
2007-11-17 6:45 ` Dane Mutters
2007-11-17 7:44 ` Peter Zijlstra [this message]
2007-11-17 10:39 ` Alan Cox
2007-11-17 13:36 ` Andi Kleen
2007-11-17 15:28 ` Herbert Xu
2007-11-17 17:42 ` Martin Olsson
2007-11-17 10:03 ` Peter Zijlstra
2007-11-17 15:53 ` Diego Calleja
2007-11-17 17:55 ` Dane Mutters
2007-11-23 7:34 ` Radoslaw Szkodzinski
2007-11-22 0:05 ` (``-_-´´) -- Fernando
2007-11-22 12:03 ` David Newall
2007-11-16 21:38 ` Diego Calleja
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=1195285481.3059.12.camel@twins \
--to=peterz@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmutters@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnemo@minimum.se \
--cc=ubuntu-devel-discuss@lists.ubuntu.com \
/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