From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Jan Engelhardt" <jengelh@linux01.gwdg.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Miklos Szeredi" <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, util-linux-ng@vger.kernel.org,
containers@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/8] unprivileged mount syscall
Date: Fri, 6 Apr 2007 22:40:20 -0500 [thread overview]
Message-ID: <a4e6962a0704062040q12c0013ek9591b9fbb27caa12@mail.gmail.com> (raw)
In-Reply-To: <4616E459.1090409@zytor.com>
On 4/6/07, H. Peter Anvin <hpa@zytor.com> wrote:
> Jan Engelhardt wrote:
> > On Apr 6 2007 16:16, H. Peter Anvin wrote:
> >>>> - users can use bind mounts without having to pre-configure them in
> >>>> /etc/fstab
> >>>>
> >> This is by far the biggest concern I see. I think the security implication of
> >> allowing anyone to do bind mounts are poorly understood.
> >
> > $ whoami
> > miklos
> > $ mount --bind / ~/down_under
> >
> > later that day:
> > # userdel -r miklos
> >
>
> Consider backups, for example.
>
This is the reason why enforcing private namespaces for user mounts
makes sense. I think it catches many of these corner cases.
-eric
next prev parent reply other threads:[~2007-04-07 3:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070404183012.429274832@szeredi.hu>
2007-04-06 23:02 ` Andrew Morton
2007-04-06 23:16 ` H. Peter Anvin
2007-04-06 23:55 ` Jan Engelhardt
2007-04-07 0:22 ` H. Peter Anvin
2007-04-07 3:40 ` Eric Van Hensbergen [this message]
2007-04-07 6:48 ` Miklos Szeredi
2007-04-10 8:52 ` Ian Kent
2007-04-11 10:48 ` Miklos Szeredi
2007-04-11 13:48 ` Ian Kent
2007-04-11 14:26 ` Serge E. Hallyn
2007-04-11 14:27 ` Ian Kent
2007-04-11 14:45 ` Serge E. Hallyn
2007-04-07 6:41 ` Miklos Szeredi
2007-04-09 14:38 ` Serge E. Hallyn
2007-04-09 16:24 ` Miklos Szeredi
2007-04-09 17:07 ` Serge E. Hallyn
2007-04-09 17:46 ` Ram Pai
2007-04-09 18:25 ` H. Peter Anvin
2007-04-10 10:33 ` Karel Zak
2007-04-09 20:10 ` Miklos Szeredi
2007-04-10 8:38 ` Ram Pai
2007-04-11 10:44 ` Miklos Szeredi
2007-04-11 18:28 ` Ram Pai
2007-04-13 11:58 ` Miklos Szeredi
2007-04-13 13:28 ` Serge E. Hallyn
2007-04-13 14:05 ` Miklos Szeredi
2007-04-13 21:44 ` Serge E. Hallyn
2007-04-15 20:39 ` Miklos Szeredi
2007-04-16 1:11 ` Serge E. Hallyn
2007-04-16 8:18 ` Ram Pai
2007-04-16 9:27 ` Miklos Szeredi
2007-04-16 15:40 ` Eric W. Biederman
2007-04-16 15:55 ` Miklos Szeredi
2007-04-13 20:07 ` Karel Zak
2007-04-15 20:21 ` Miklos Szeredi
2007-04-16 7:59 ` Ram Pai
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=a4e6962a0704062040q12c0013ek9591b9fbb27caa12@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=util-linux-ng@vger.kernel.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 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®