mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Michael j Theall <mtheall@us.ibm.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
	fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
	"Serge H. Hallyn" <serge.hallyn@ubuntu.com>
Subject: Re: [fuse-devel] [PATCH v4 4/5] fuse: Support privileged xattrs only	with a mount option
Date: Tue, 14 Oct 2014 13:01:02 -0700	[thread overview]
Message-ID: <878ukis9oh.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <OFD40DA8DF.F78EA39D-ON86257D71.0057C4DC-86257D71.0064055D@us.ibm.com> (Michael j. Theall's message of "Tue, 14 Oct 2014 13:12:26 -0500")

Michael j Theall <mtheall@us.ibm.com> writes:

> Seth Forshee <seth.forshee@canonical.com> wrote on 10/14/2014 09:25:55 AM:
>
>> From: Seth Forshee <seth.forshee@canonical.com>
>> To: Miklos Szeredi <miklos@szeredi.hu>
>> Cc: fuse-devel@lists.sourceforge.net, "Serge H. Hallyn" 
>> <serge.hallyn@ubuntu.com>, linux-kernel@vger.kernel.org, Seth 
>> Forshee <seth.forshee@canonical.com>, "Eric W. Biederman" 
>> <ebiederm@xmission.com>, linux-fsdevel@vger.kernel.org
>> Date: 10/14/2014 09:27 AM
>> Subject: [fuse-devel] [PATCH v4 4/5] fuse: Support privileged xattrs
>> only with a mount option
>> 
>> Allowing unprivileged users to provide arbitrary xattrs via fuse
>> mounts bypasses the normal restrictions on setting xattrs. Such
>> mounts should be restricted to reading and writing xattrs in the
>> user.* namespace.
>> 
>
> Can you explain how the normal restrictions on setting xattrs are 
> bypassed?

If the fuse server is not run by root.  Which is a large part of the
point of fuse.

> My filesystem still needs security.* and system.*, and it looks like
> xattr_permission already prevents non-privileged users from accessing
> trusted.*

If the filesystem is mounted with nosuid (typical of a non-privileged
mount of fuse) then the security.* attributes are ignored.

>> It's difficult though to tell whether a mount is being performed
>> on behalf of an unprivileged user since fuse mounts are ususally
>> done via a suid root helper. Thus a new mount option,
>> privileged_xattrs, is added to indicated that xattrs from other
>> namespaces are allowed. This option can only be supplied by
>> system-wide root; supplying the option as an unprivileged user
>> will cause the mount to fail.
>
> I can't say I'm convinced that this is the right direction to head.

With respect to defaults we could keep the current default if you
have the global CAP_SYS_ADMIN privilege when the mount takes place
and then avoid breaking anything.

Eric

  reply	other threads:[~2014-10-14 20:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 14:25 [PATCH v4 0/5] fuse: Add support for mounts from pid/user namespaces Seth Forshee
2014-10-14 14:25 ` [PATCH v4 1/5] fuse: Add support for pid namespaces Seth Forshee
2014-10-14 14:25 ` [PATCH v4 2/5] fuse: Support fuse filesystems outside of init_user_ns Seth Forshee
2014-10-15 14:49   ` Andy Lutomirski
2014-10-15 15:05     ` Seth Forshee
2014-10-15 17:05       ` Andy Lutomirski
2014-10-15 22:59         ` Seth Forshee
2014-10-15 23:07           ` Andy Lutomirski
2014-10-15 23:24             ` Seth Forshee
2014-10-14 14:25 ` [PATCH v4 3/5] fuse: Restrict allow_other to uids already controlled by the user Seth Forshee
2014-10-15 14:58   ` Andy Lutomirski
2014-10-15 15:11     ` Seth Forshee
2014-10-14 14:25 ` [PATCH v4 4/5] fuse: Support privileged xattrs only with a mount option Seth Forshee
2014-10-14 18:12   ` [fuse-devel] " Michael j Theall
2014-10-14 20:01     ` Eric W. Biederman [this message]
2014-10-14 20:59       ` Seth Forshee
2014-10-14 21:13         ` Eric W. Biederman
2014-10-14 21:19           ` Andy Lutomirski
2014-10-14 21:29             ` Eric W. Biederman
2014-10-15  7:39             ` Seth Forshee
2014-10-15 14:37               ` Andy Lutomirski
2014-10-21 21:21                 ` Seth Forshee
2014-10-21 21:27                   ` Andy Lutomirski
2014-10-21 21:34                     ` Michael j Theall
2014-10-21 21:44                       ` Andy Lutomirski
2014-10-22  4:58                     ` Seth Forshee
2014-10-23 18:32                       ` Andy Lutomirski
2014-10-23 21:24                         ` Seth Forshee
2014-10-14 14:25 ` [PATCH v4 5/5] fuse: Allow user namespace mounts Seth Forshee
2014-10-15 14:58   ` Andy Lutomirski
2014-10-15 15:20     ` Seth Forshee
2014-10-15 23:08       ` Andy Lutomirski
2014-10-15 23:07     ` Seth Forshee

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=878ukis9oh.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mtheall@us.ibm.com \
    --cc=serge.hallyn@ubuntu.com \
    --cc=seth.forshee@canonical.com \
    /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

Powered by JetHome