From: starlight@binnacle.cx
To: linux-kernel@vger.kernel.org
Subject: suggestion: msgctl(IPC_RMID) req CAP_IPC_OWNER instead of CAP_SYS_ADMIN
Date: Sat, 02 Jan 2010 01:01:05 -0500 [thread overview]
Message-ID: <6.2.5.6.2.20100102005433.03a07f40@flumedata.com> (raw)
Hello,
We have a service daemon that must on occasion clean up orphaned
SVR4/POSIX message queues left over by dead client processes.
The service daemon runs with least privileges, and it receives a
small set of capabilities that its job demands.
However I was surprised to see that CAP_SYS_ADMIN is needed when
using IPC_RMID to remove message queues owned by other user
IDs. This is a powerful and dangerous privilege and I dislike
assigning it to the daemon. Seems to me that CAP_IPC_OWNER is a
better fit for this function.
This is just a suggestion. Please respond with my e-mail CCed
as I am not a list subscriber.
Regards
reply other threads:[~2010-01-02 6:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6.2.5.6.2.20100102005433.03a07f40@flumedata.com \
--to=starlight@binnacle.cx \
--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®