From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RLIMIT_NPROC enforcement during execve() calls
Date: Mon, 18 Apr 2005 20:07:04 +0200 [thread overview]
Message-ID: <1113847624.17341.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20050418174346.GA28790@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
El lun, 18-04-2005 a las 18:43 +0100, Christoph Hellwig escribió:
> On Mon, Apr 18, 2005 at 07:38:57PM +0200, Lorenzo Hern?ndez Garc?a-Hierro wrote:
> > Enforces the RLIMIT_NPROC limit by adding an additional check for
> > execve(), as
> > such limit is checked only during fork() calls.
>
> What's the point? exec doesn't create new process and exec() shouldn't
> start to fail just because someone lowered the rlimit a short while ago.
The limit is only checked when process is created on a fork() call, but
during execution it's uid can change, thus, the limit for the new uid
could be exceed.
It comes from the Openwall kernel patch, as well implemented in
grSecurity and vSecurity.
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-18 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 17:38 [PATCH] RLIMIT_NPROC enforcement during execve() calls Lorenzo Hernández García-Hierro
2005-04-18 17:43 ` Christoph Hellwig
2005-04-18 18:07 ` Lorenzo Hernández García-Hierro [this message]
2005-04-18 21:15 ` Valdis.Kletnieks
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=1113847624.17341.36.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.