mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: hch@infradead.org, trond.myklebust@fys.uio.no,
	adilger@clusterfs.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [patch 2/2] VFS: allow filesystem to override mknod capability checks
Date: Mon, 24 Sep 2007 13:38:13 +0100	[thread overview]
Message-ID: <20070924123813.GB17409@infradead.org> (raw)
In-Reply-To: <E1IZn0c-0003qS-00@dorka.pomaz.szeredi.hu>

On Mon, Sep 24, 2007 at 02:25:54PM +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
> 
> Add a new super block flag, that results in the VFS not checking if
> the current process has enough privileges to do an mknod().
> 
> If this flag is set, all mounts for this super block will have the
> "nodev" flag implied.
> 
> This is needed on filesystems, where an unprivileged user may be able
> to create a device node, without causing security problems.
> 
> One such example is "mountlo" a loopback mount utility implemented
> with fuse and UML, which runs as an unprivileged userspace process.
> In this case the user does in fact have the right to create device
> nodes within the filesystem image, as long as the user has write
> access to the image.  Since the filesystem is mounted with "nodev",
> adding device nodes is not a security concern.

This one looks okay, but I'd prefer to not put it in until we actually
have proper non-privilegued mounts.


  reply	other threads:[~2007-09-24 12:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 12:24 [patch 1/2] VFS: new fgetattr() file operation Miklos Szeredi
2007-09-24 12:25 ` [patch 2/2] VFS: allow filesystem to override mknod capability checks Miklos Szeredi
2007-09-24 12:38   ` Christoph Hellwig [this message]
2007-09-28  2:40   ` Neil Brown
2007-10-01 18:06     ` Miklos Szeredi
2007-09-24 12:36 ` [patch 1/2] VFS: new fgetattr() file operation Christoph Hellwig
2007-09-24 12:48   ` Miklos Szeredi
2007-09-24 12:59     ` Matthew Wilcox
2007-09-24 13:06       ` Miklos Szeredi
2007-09-24 13:10         ` Christoph Hellwig
2007-09-24 13:18           ` Miklos Szeredi
2007-09-24 13:27             ` Christoph Hellwig
2007-09-24 13:38               ` Miklos Szeredi
2007-09-24 13:16         ` Matthew Wilcox
2007-09-24 13:21           ` Miklos Szeredi
2007-09-24 13:42     ` Alan Cox
2007-09-24 13:40       ` Miklos Szeredi

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=20070924123813.GB17409@infradead.org \
    --to=hch@infradead.org \
    --cc=adilger@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=trond.myklebust@fys.uio.no \
    /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®