From: knobo@linpro.no
To: linux-kernel@vger.kernel.org
Subject: [BUG] capabilities
Date: 28 Feb 2002 15:02:49 +0100 [thread overview]
Message-ID: <ujpu1s1901i.fsf@ping.linpro.no> (raw)
Hi,
Dropping the capability CAP_FSETID by itself does not work (and that
is probably correct), but when I drop CAP_CHOWN, CAP_FSETID works for
the group id, but not user id. I guess this is a bug (ref
include/linux/capability.h).
It does not look like dropping the CAP_SETGID (dropping CAP_SETGID
works in combination with dropping CAP_CHOWN) and CAP_SETUID works
either. Maybe they need to be dropped in combination with some other
capability? If so, it shod be more clear in the documentation
(cabability.h).
--
Knut Olav Bøhmer
_ _
/ / (_)__ __ ____ __
/ /__/ / _ \/ // /\ \/ / ... The choice of a
/____/_/_//_/\.,_/ /_/\.\ GNU generation
export PAGER="od -x |less"
reply other threads:[~2002-02-28 14:07 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=ujpu1s1901i.fsf@ping.linpro.no \
--to=knobo@linpro.no \
--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