From: David Howells <dhowells@redhat.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: dhowells@redhat.com, Stephen Smalley <sds@tycho.nsa.gov>,
viro@ftp.linux.org.uk, hch@infradead.org,
Trond.Myklebust@netapp.com, casey@schaufler-ca.com,
linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 2/3] CRED: Split the task security data and move part of it into struct cred
Date: Mon, 24 Sep 2007 16:52:55 +0100 [thread overview]
Message-ID: <11732.1190649175@redhat.com> (raw)
In-Reply-To: <20070924153541.GB26258@vino.hallyn.com>
Serge E. Hallyn <serge@hallyn.com> wrote:
> Ah, ok, so the daemon would use this to act under the user's
> credentials. I was thinking the user would be using this to act
> under the daemon's or kernel's sid.
Think kernel service rather than daemon. NFSd provides its own daemons to
override the security of, whereas cachefiles runs in the process context of
whoever called NFS.
> Between that and David's response, that this is only for the duration of
> one syscall (IIUC),
That's more or less correct. You have to add the pagefault handler to that
list.
> My worry arose from the fact that I don't see
> security_cred_kernel_act_as() being called anywhere in this patchset...
Look in:
[PATCH 04/22] CRED: Request a credential record for a kernel service
Which was part of a patchset I sent on the 21st Sept. get_kernel_cred() is in
turn used by:
[PATCH 13/22] CacheFiles: A cache that backs onto a mounted filesystem
David
next prev parent reply other threads:[~2007-09-24 15:53 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 [this message]
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 8:15 ` David Howells
2007-09-20 13:38 ` Trond Myklebust
2007-09-20 15:36 ` Casey Schaufler
2007-09-20 16:09 ` Trond Myklebust
2007-09-26 18:23 ` Al Viro
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=11732.1190649175@redhat.com \
--to=dhowells@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=casey@schaufler-ca.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--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