From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Max Valdez <maxvalde@fis.unam.mx>
Cc: system_lists@nullzone.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Forking shell bombs
Date: 08 Jul 2003 23:25:01 +0100 [thread overview]
Message-ID: <1057703101.5652.12.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <1057684703.6241.3.camel@garaged.homeip.net>
On Maw, 2003-07-08 at 18:18, Max Valdez wrote:
> I set the ulimit -u 1791
> and the box keeps running(2.4.20-gentoo-r5) , but we still need the
> problem corrected, any other user can run ther DOS and crash the box, is
> there any way to set ulimits for all users fixed ??, not by sourcein a
> bashrc or something like that ?? because the user can delete the line on
> .bashrc and thats it
You can set the limits using the pam limits module and set the hard
limit so the user cannot revert it. Or with -ac just set no overcommit
and it seems fine
next prev parent reply other threads:[~2003-07-08 22:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 20:28 Ryan Underwood
2003-07-08 20:37 ` vlad
2003-07-08 20:43 ` jhigdon
2003-07-08 21:25 ` Ryan Underwood
2003-07-08 22:43 ` Sir Ace
2003-07-09 15:07 ` David Ford
2003-07-09 21:10 ` Ryan Underwood
2003-07-13 9:10 ` Riley Williams
2003-07-13 9:40 ` Jan-Benedict Glaw
2003-07-13 14:17 ` Gene Heskett
2003-07-08 21:59 ` system_lists
2003-07-08 17:18 ` Max Valdez
2003-07-08 22:25 ` Alan Cox [this message]
2003-07-08 22:26 ` Svein Ove Aas
2003-07-08 22:51 ` Ryan Underwood
2003-07-10 12:32 ` Luiz Capitulino
2003-07-08 23:05 ` Wakko Warner
2003-07-09 11:36 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 11:05 Arvind Kandhare
2003-07-08 22:26 Perez-Gonzalez, Inaky
2003-07-08 18:45 Ryan Underwood
2003-07-08 18:55 ` Charles Cazabon
2003-07-08 22:01 ` Alan Cox
2003-07-08 19:23 ` jhigdon
2003-07-08 20:35 ` vlad
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=1057703101.5652.12.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maxvalde@fis.unam.mx \
--cc=system_lists@nullzone.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®