From: Felix von Leitner <felix-kernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: request: capabilities that allow users to drop privileges further
Date: Mon, 15 Dec 2003 22:39:12 +0100 [thread overview]
Message-ID: <20031215213912.GA29281@codeblau.de> (raw)
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
* fork
* execve
* ptrace
* load kernel modules
* mknod
* write to the file system
and I would like to modify my smtpd to not be able to
* fork
* execve
* ptrace
* load kernel modules
* mknod
I can kludge around some of these, for example I can disable fork with
resource limits, and I can limit writing to the file system with chroot
and proper permissions in the file systems, but I'm not aware of a way
to disable ptrace for example, or pthread_create.
I know that there are patches to provide an extended "jail" chroot
support, but being able to drop capabilities like this would be a more
general solution.
Felix
next reply other threads:[~2003-12-15 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 21:39 Felix von Leitner [this message]
2003-12-15 22:10 ` request: capabilities that allow users to drop privileges further 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
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=20031215213912.GA29281@codeblau.de \
--to=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 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.