From: Chris Wright <chrisw@osdl.org>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: request: capabilities that allow users to drop privileges further
Date: Mon, 15 Dec 2003 14:48:09 -0800 [thread overview]
Message-ID: <20031215144809.A14552@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <20031215213912.GA29281@codeblau.de>; from felix-kernel@fefe.de on Mon, Dec 15, 2003 at 10:39:12PM +0100
* Felix von Leitner (felix-kernel@fefe.de) wrote:
> I would like to be able to drop capabilities that every normal user has,
> so that network servers can limit the impact of possible future security
> problems further. For example, I want my non-cgi web server to be able
> to drop the capabilities to
Using existing capabilities system you can limit many of these. Just
dropping privs from uid = 0 to anything else is a good start.
> * fork
rlimit
> * execve
mount fs noexec
> * ptrace
drop CAP_SYS_PTRACE
> * load kernel modules
drop CAP_SYS_MODULE
> * mknod
drop CAP_MKNOD
> * write to the file system
mount fs r/o.
In general, most of what you ask for is already there. Otherwise use
some MAC policy that gives you the control you want (check out SELinux
for example).
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-12-15 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 21:39 Felix von Leitner
2003-12-15 22:10 ` Richard B. Johnson
2003-12-15 22:55 ` Christian Borntraeger
2003-12-16 14:08 ` Martin Waitz
2003-12-15 22:34 ` Christian Borntraeger
2003-12-15 22:48 ` Chris Wright [this message]
2003-12-16 14:13 ` Martin Waitz
2003-12-17 1:30 ` Felix von Leitner
2003-12-17 1:41 ` Chris Wright
2003-12-16 13:27 ` James Morris
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=20031215144809.A14552@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=felix-kernel@fefe.de \
--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 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®