From: don-linux@isis.cs3-inc.com (Don Cohen)
To: Andrew Morgan <morgan@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: execve setting capabilities incorrectly ?
Date: Tue, 14 Jan 2003 10:47:17 -0800 [thread overview]
Message-ID: <15908.23349.763824.371300@isis.cs3-inc.com> (raw)
In-Reply-To: <3E245481.5050606@transmeta.com>
Andrew Morgan writes:
> execcap doesn't work...
Thanks.
Could I suggest appropriate updates to
http://ftp.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.4/capfaq-0.2.txt
(which caused me to waste a day or so).
I hope the people who can make such updates read this list.
I'd also appreciate pointers to other mechanisms for accomplishing the
same goals. (And perhaps these belong in the above update too.)
Which still leaves the question of what strace has to do with it.
prev parent reply other threads:[~2003-01-14 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 18:00 execve setting capabilities incorrectly ? Don Cohen
2003-01-14 18:18 ` Andrew Morgan
2003-01-14 18:47 ` Don Cohen [this message]
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=15908.23349.763824.371300@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;
as well as URLs for NNTP newsgroup(s).