From: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
To: Linda Walsh <lkml@tlinx.org>
Cc: util-linux@vger.kernel.org
Subject: Re: Utilities don't take into account capabilities
Date: Mon, 18 Aug 2014 00:57:30 +0000 (GMT) [thread overview]
Message-ID: <fb20984219ad.53f14f7a@langara.bc.ca> (raw)
In-Reply-To: <53F11687.5060805@tlinx.org>
> Seriously... What capabilities does mount need in order to function?
I can help out with this one.
> CAP_SYS_ADMIN
> * Perform a range of system administration operations including:
quotactl(2),
> mount(2), umount(2), swapon(2), swapoff(2), sethostname(2), and
setdomain‐
> name(2);
> * perform privileged syslog(2) operations (since Linux 2.6.37,
CAP_SYSLOG should
> be used to permit such operations);
> * perform IPC_SET and IPC_RMID operations on arbitrary System V IPC
objects;
> * perform operations on trusted and security Extended Attributes (see
attr(5));
> * use lookup_dcookie(2);
> * use ioprio_set(2) to assign IOPRIO_CLASS_RT and (before Linux
2.6.25)
> IOPRIO_CLASS_IDLE I/O scheduling classes;
> * forge UID when passing socket credentials;
> * exceed /proc/sys/fs/file-max, the system-wide limit on the
number of open
> files, in system calls that open files (e.g., accept(2), execve(2),
open(2),
> pipe(2));
> * employ CLONE_NEWNS flag with clone(2) and unshare(2);
> * call setns(2);
> * perform KEYCTL_CHOWN and KEYCTL_SETPERM keyctl(2) operations;
> * perform madvise(2) MADV_HWPOISON operation.
>From CAPABILITIES(7) in the Linux Programmer's Manual.
next prev parent reply other threads:[~2014-08-18 0:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 21:57 Utilities don't take into account capabilities Steven Stewart-Gallus
2014-08-17 20:54 ` Linda Walsh
2014-08-18 0:57 ` Steven Stewart-Gallus [this message]
2014-08-18 1:23 ` Linda Walsh
2014-08-18 14:47 ` Dale R. Worley
2014-08-18 19:19 ` Linda Walsh
2014-08-18 21:57 ` Dale R. Worley
2014-08-18 12:05 ` Mike Frysinger
2014-08-18 17:40 ` Steven Stewart-Gallus
2014-08-19 9:07 ` Karel Zak
2014-08-19 21:54 ` Steven Stewart-Gallus
2014-08-22 0:38 ` Linda Walsh
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=fb20984219ad.53f14f7a@langara.bc.ca \
--to=sstewartgallus00@mylangara.bc.ca \
--cc=lkml@tlinx.org \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).