public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: redoubtable <redoubtable@netcabo.pt>
To: undisclosed-recipients:;
Subject: fork()
Date: Thu, 24 Mar 2005 16:45:55 +0000	[thread overview]
Message-ID: <4242EEC3.2000605@netcabo.pt> (raw)

Hey,

I read a document on securityfocus about fork bombinb a linux system. 
Although they didn't speak about the effectiveness of resource limits I 
guess that should be discussed because it's possible to make a linux 
machine extremely slow (compared to FreeBSD for instance) even with well 
configured resource limits.
I revised kernel/fork.c and I found a way to prevent this problem by 
removing all associated processes with the parent, but that's far from 
portable and should not be used for the sake of compatibilities. I guess 
the function fork() should be revised.
And what about creating a 'maxprocs' sysctl var (even if left high) when 
the resource limits problem is fixed? It would help security when it is 
needed and wouldn't bother other applications. RLIMITs on login are not 
trustworthy. It should exist a global limit in case someone could spawn 
a shell without limits through some flawed application.

Thanks, and please advise.


             reply	other threads:[~2005-03-24 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 16:45 redoubtable [this message]
2005-03-24 18:17 ` fork() Triffid Hunter
2005-03-25  7:28   ` fork() Natanael Copa

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=4242EEC3.2000605@netcabo.pt \
    --to=redoubtable@netcabo.pt \
    /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