From: Chris Wright <chrisw@osdl.org>
To: Alexander Nyberg <alexn@telia.com>
Cc: Chris Wright <chrisw@osdl.org>,
Manfred Georg <mgeorg@arl.wustl.edu>,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capabilities not inherited
Date: Wed, 8 Jun 2005 14:59:04 -0700 [thread overview]
Message-ID: <20050608215904.GE13152@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1118265642.969.12.camel@localhost.localdomain>
* Alexander Nyberg (alexn@telia.com) wrote:
> btw since the last discussion was about not changing the existing
> interface and thus exposing security flaws, what about introducing
> another prctrl that says maybe PRCTRL_ACROSS_EXECVE?
It's not ideal (as you mention, mess upon mess), but maybe it is the
sanest way to go forward.
> Any new user-space applications must understand the implications of
> using it so it's safe in that aspect. Yes?
At least less-likely to surprise ;-)
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-06-08 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 20:27 [PATCH] capabilities not inherited Manfred Georg
2005-06-08 20:41 ` Alexander Nyberg
2005-06-08 21:26 ` Manfred Georg
2005-06-08 20:44 ` Chris Wright
2005-06-08 21:20 ` Alexander Nyberg
2005-06-08 21:33 ` Manfred Georg
2005-06-08 21:46 ` Alexander Nyberg
2005-06-08 21:54 ` Chris Wright
2005-06-08 21:59 ` Chris Wright [this message]
2005-06-08 23:49 ` Lee Revell
2005-06-09 2:59 ` David Wagner
2005-06-09 10:32 ` Alexander Nyberg
2005-06-09 14:55 ` David Wagner
2005-06-09 15:31 ` Lee Revell
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=20050608215904.GE13152@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=alexn@telia.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgeorg@arl.wustl.edu \
/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