From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] rlimit_nproc check
Date: Sun, 12 Jun 2011 17:12:24 +0400 [thread overview]
Message-ID: <20110612131223.GA3994@albatros> (raw)
In-Reply-To: <20110612022833.GB14976@openwall.com>
Solar,
On Sun, Jun 12, 2011 at 06:28 +0400, Solar Designer wrote:
> As an option, you could propose to revert that 8-year old change and
> introduce the check on execve(). Unrealistic?
I've started a separate thread on LKML for it, we'll see ;)
> Oh, by the way, here's what I found:
>
> Subject: [PATCH] sched: Don't allow setuid to succeed if the user does not have rt bandwidth
> http://lists.openwall.net/linux-kernel/2009/02/27/177
Yeah, but it was removed in 7c9414385ebfdd87cc542d4e7e3bb0dbb2d3ce25 as
a "2.6.34 scheduled cleanup".
Thanks,
--
Vasiliy
next prev parent reply other threads:[~2011-06-12 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 14:17 [kernel-hardening] rlimit_nproc check Vasiliy Kulikov
2011-06-12 2:28 ` Solar Designer
2011-06-12 13:12 ` Vasiliy Kulikov [this message]
2011-06-19 13:34 ` Vasiliy Kulikov
2011-06-23 17:11 ` Vasiliy Kulikov
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=20110612131223.GA3994@albatros \
--to=segoon@openwall.com \
--cc=kernel-hardening@lists.openwall.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