From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Patch for restorecond to not report an error if filesystem does not support XATTR
Date: Fri, 01 Dec 2006 22:37:41 -0500 [thread overview]
Message-ID: <4570F505.5050305@tresys.com> (raw)
In-Reply-To: <1164913329.23019.978.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>
> Interesting question...the policy Makefile and the fixfiles script have
> always just used a hardcoded list of filesystem types known to support
> file security labeling. And the policy configuration explicitly
> specifies the filesystem types for which SELinux tries to use xattrs, as
> the mere presence of an xattr handler has never been a sufficient test.
> Possibly we should be extracting that list from policy and making it
> available for programs that need to know it.
>
> Even testing the result of setxattr for EOPNOTSUPP is not 100%, as
> setxattr will also fall back to setting the incore value if a) you pass
> permission checks and b) the filesystem provides no setxattr method at
> all (NFS happens to provide one, but it only supports ACLs). So it
> could succeed (e.g. devpts nodes) or fail with -EACCES (e.g. proc).
>
Can we make an selinuxfs node that just outputs the list of fs_use_xattr
filesystems?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-12-02 3:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 22:18 Patch for restorecond to not report an error if filesystem does not support XATTR Daniel J Walsh
2006-11-30 16:25 ` Joshua Brindle
2006-11-30 17:06 ` Daniel J Walsh
2006-11-30 18:15 ` Joshua Brindle
2006-11-30 19:02 ` Stephen Smalley
2006-12-02 3:37 ` Joshua Brindle [this message]
2006-12-04 20:10 ` Stephen Smalley
2006-12-06 17:19 ` Karl MacMillan
2006-12-12 18:18 ` Stephen Smalley
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=4570F505.5050305@tresys.com \
--to=jbrindle@tresys.com \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.