From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Paris <eparis@parisplace.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] fuse: Only allow read/writing user xattrs
Date: Sat, 06 Oct 2012 08:34:09 -0700 [thread overview]
Message-ID: <87a9vzlimm.fsf@xmission.com> (raw)
In-Reply-To: <CACLa4pue6Bb-37+u03C4=yva=SKDhxNyZyVgvv5dAmt-1ryzBQ@mail.gmail.com> (Eric Paris's message of "Sat, 6 Oct 2012 10:23:02 -0400")
Eric Paris <eparis@parisplace.org> writes:
> NAK, this makes no sense... We are working to support SELinux
> attrs on fuse, why shouldn't we?
Certainly there is a logical disconnect here.
What is the sense in security labels when anyone can arbitrarily choose
the security label they want and change the security label whenever
they want?
What is the point in a security label when you can not trust it?
Eric
next prev parent reply other threads:[~2012-10-06 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 22:50 [PATCH] fuse: Only allow read/writing user xattrs Eric W. Biederman
2012-10-06 14:23 ` Eric Paris
2012-10-06 15:34 ` Eric W. Biederman [this message]
2012-10-06 15:57 ` Eric Paris
2012-10-06 23:42 ` Eric W. Biederman
2012-10-08 13:47 ` Serge Hallyn
2012-10-08 14:02 ` Eric Paris
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=87a9vzlimm.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=eparis@parisplace.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.