From: Lukasz Pawelczyk <l.pawelczyk@samsung.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
Miklos Szeredi <mszeredi@suse.cz>,
Lukasz Pawelczyk <havner@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Mark Rustad <mark.d.rustad@intel.com>,
Matthew Dempsky <mdempsky@chromium.org>,
Richard Weinberger <richard@nod.at>,
Daeseok Youn <daeseok.youn@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
David Rientjes <rientjes@google.com>,
Alex Thorlton <athorlton@sgi.com>,
Juri Lelli <juri.lelli@gmail.com>,
Kees Cook <keescook@chromium.org>,
Nikolay Aleksandrov <nikolay@redhat.com>,
Dario Faggioli <raistlin@linux.it>,
Al Viro <viro@zeniv.linux.org.uk>,
James Morris <james.l.morris@oracle.com>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>, Paul Moore <pmoore@redhat.com>,
linux-security-module@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] lsm: namespace hooks
Date: Tue, 02 Dec 2014 13:43:13 +0100 [thread overview]
Message-ID: <1417524193.1899.2.camel@samsung.com> (raw)
In-Reply-To: <1417109911.1805.27.camel@samsung.com>
On czw, 2014-11-27 at 18:38 +0100, Lukasz Pawelczyk wrote:
> Right now the major issue I see is that LSM by itself is not defined how
> it's going to behave. It's up to a specific LSM module.
>
> E.g. within the Smack namespace filling the map is a privileged
> operation. So by tying them up you cripple the ability to create a fully
> working user namespace as an unprivileged process.
Entertaining the idea that LSM namespace would be tied to user namespace
(as you suggested) how do you see the limitation I described above?
--
Lukasz Pawelczyk
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2014-12-02 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 14:01 [RFC] LSM/Smack namespace work in progress Lukasz Pawelczyk
2014-11-27 14:01 ` [RFC] lsm: namespace hooks Lukasz Pawelczyk
2014-11-27 14:18 ` Richard Weinberger
2014-11-27 14:35 ` Lukasz Pawelczyk
[not found] ` <54773757.8090905@nod.at>
2014-11-27 14:44 ` Lukasz Pawelczyk
[not found] ` <54773CE7.5040303@nod.at>
2014-11-27 15:11 ` Lukasz Pawelczyk
[not found] ` <547740A0.4040700@nod.at>
2014-11-27 15:24 ` Lukasz Pawelczyk
2014-11-27 15:42 ` Eric W. Biederman
2014-11-27 16:07 ` Lukasz Pawelczyk
2014-11-27 16:44 ` Eric W. Biederman
2014-11-27 17:38 ` Lukasz Pawelczyk
2014-12-02 12:43 ` Lukasz Pawelczyk [this message]
2014-12-09 16:13 ` Eric W. Biederman
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=1417524193.1899.2.camel@samsung.com \
--to=l.pawelczyk@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=casey@schaufler-ca.com \
--cc=containers@lists.linux-foundation.org \
--cc=daeseok.youn@gmail.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=havner@gmail.com \
--cc=james.l.morris@oracle.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=juri.lelli@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mdempsky@chromium.org \
--cc=mingo@redhat.com \
--cc=mszeredi@suse.cz \
--cc=nikolay@redhat.com \
--cc=oleg@redhat.com \
--cc=pmoore@redhat.com \
--cc=raistlin@linux.it \
--cc=richard@nod.at \
--cc=rientjes@google.com \
--cc=vdavydov@parallels.com \
--cc=viro@zeniv.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