From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: casey@schaufler-ca.com
Cc: Andrew Morgan <morgan@kernel.org>,
David Howells <dhowells@redhat.com>,
viro@ftp.linux.org.uk, hch@infradead.org, sds@tycho.nsa.gov,
linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 3/3] CRED: Move the effective capabilities into the cred struct
Date: Thu, 20 Sep 2007 12:09:06 -0400 [thread overview]
Message-ID: <1190304546.6763.86.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <176624.5520.qm@web36603.mail.mud.yahoo.com>
On Thu, 2007-09-20 at 08:36 -0700, Casey Schaufler wrote:
> Ok, what can't be copied, and why can't it be copied?
In practice, no security information can be copied because the checks
are all made on the "current" pointer. There is no mechanism other than
'current' for passing security information around.
Trond
next prev parent reply other threads:[~2007-09-20 16:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 16:17 [PATCH 0/3] Introduce credential record David Howells
2007-09-19 16:17 ` [PATCH 1/3] CRED: Introduce a COW credentials record David Howells
2007-09-19 16:18 ` [PATCH 2/3] CRED: Split the task security data and move part of it into struct cred David Howells
2007-09-19 17:28 ` Casey Schaufler
2007-09-19 22:57 ` David Howells
2007-09-20 16:31 ` Casey Schaufler
2007-09-20 17:17 ` David Howells
2007-09-20 17:33 ` David Howells
2007-09-24 14:00 ` Serge E. Hallyn
2007-09-24 14:21 ` Stephen Smalley
2007-09-24 15:35 ` Serge E. Hallyn
2007-09-24 15:52 ` David Howells
2007-09-26 13:30 ` David Howells
2007-09-26 14:14 ` Stephen Smalley
2007-09-26 14:58 ` Casey Schaufler
2007-09-19 16:18 ` [PATCH 3/3] CRED: Move the effective capabilities into the cred struct David Howells
2007-09-20 4:11 ` Andrew Morgan
2007-09-20 13:38 ` Trond Myklebust
2007-09-20 15:36 ` Casey Schaufler
2007-09-20 16:09 ` Trond Myklebust [this message]
2007-09-26 18:23 ` Al Viro
2007-09-20 8:15 ` David Howells
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=1190304546.6763.86.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=viro@ftp.linux.org.uk \
/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®