From: don-linux@isis.cs3-inc.com (Don Cohen)
To: linux-kernel@vger.kernel.org
Cc: morgan@transmeta.com
Subject: execve setting capabilities incorrectly ?
Date: Tue, 14 Jan 2003 10:00:32 -0800 [thread overview]
Message-ID: <200301141800.h0EI0WS13467@isis.cs3-inc.com> (raw)
Please cc me in replies.
quoting from message dated 1998/06 to this list from Andrew Morgan
Subject: Fwd: Re: Capabilities
...
[root@godzilla progs]# ./execcap cap_net_bind_service=i sleep 1000 &
[1] 600
[root@godzilla progs]# cat /proc/600/status
...
CapInh: 0000000000000400
CapPrm: 0000000000000400
CapEff: 0000000000000400
My corresponding output ends up with
CapInh: 0000000000000400
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
I've tried in 2.4.18 and in 2.2.16, both give the same result so
I guess it's been this way for some time.
The caps seem to be set correctly by execcap but execve resets them.
Is this intentional?
If so, how is one now supposed to get the desired effects?
What's really weird (can someone explain this?) is that things
seem to work better under strace:
strace ./execcap = head <some file root has no permission to read>
=> permission denied
whereas without the strace it reads the file.
next reply other threads:[~2003-01-14 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 18:00 Don Cohen [this message]
2003-01-14 18:18 ` Andrew Morgan
2003-01-14 18:47 ` Don Cohen
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=200301141800.h0EI0WS13467@isis.cs3-inc.com \
--to=don-linux@isis.cs3-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@transmeta.com \
/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®