All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	"Eric W. Biederman"
	<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Keys and namespaces
Date: Fri, 10 Oct 2008 13:58:23 +0100	[thread overview]
Message-ID: <414.1223643503@redhat.com> (raw)
In-Reply-To: 20081010011917.GA8046@us.ibm.com


On the subject of namespaces: I still need to look at providing a key ID and
keyring name namespace.

Is it worth me just using the user_namespace?  A number of parameters are
per-UID (such as the key quotas), so it might very well make sense to do that.

That way, user_namespace could actually be a credentials namespace.

If that is the case, CLONE_NEWUSER should also set up (clone?) the keys and
keyrings attached to the parent.  This possibly needs to be done anyway as the
keys have UID and GID references that may be invalid in the new namespace.

How do the UIDs and GIDs in different namespaces map, anyway?

Furthermore, some keys may actually represent foreign user details; perhaps
NTFS or CIFS user IDs for example.  Should those be discarded on CLONE_NEWUSER?

David

  parent reply	other threads:[~2008-10-10 12:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  1:19 [PATCH RFC] User namespaces: general cleanups Serge E. Hallyn
     [not found] ` <20081010011917.GA8046-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-10 10:06   ` David Howells
     [not found]     ` <30854.1223633214-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-10-10 17:06       ` Serge E. Hallyn
2008-10-13 16:01       ` Serge E. Hallyn
     [not found]         ` <20081013160144.GA10359-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-13 21:41           ` Serge E. Hallyn
2008-10-14 17:50           ` David Howells
     [not found]             ` <29703.1224006618-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-10-14 21:43               ` Serge E. Hallyn
     [not found]             ` <20081014214327.GA28545-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-14 21:47               ` David Howells
     [not found]         ` <20081013214108.GA4701-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-13 23:10           ` David Howells
     [not found]             ` <5306.1223939456-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-10-14 14:33               ` Serge E. Hallyn
2008-10-10 12:58 ` David Howells [this message]
     [not found]   ` <414.1223643503-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-10-10 16:46     ` Keys and namespaces Serge E. Hallyn
2008-10-10 22:30     ` Eric W. Biederman
     [not found]       ` <m1hc7k13s2.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-10-13 16:27         ` Serge E. Hallyn

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=414.1223643503@redhat.com \
    --to=dhowells-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.