public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: Linux-Xfs <linux-xfs@oss.sgi.com>
Subject: choice of 'namespace' for ACL's
Date: Fri, 19 Jul 2013 01:52:47 -0700	[thread overview]
Message-ID: <51E8FE5F.8030107@tlinx.org> (raw)




I was looking at the attr and it left me a bit puzzled.

(1) Of minor consideration, was the statement about 'values can be up
to 64KB'...  But there is no mention of how many names can be present
or if there is a cumulative maximum on the names or on the data.  I thought
I remembered there was, but all I found was limits on single datums.

(2) A more confusing issue was the bit describing XFS as having 2
disjoint attrib
namespaces, but later the selectors for the names spaces are given as
[none] = user, [R] = root, and [S] = Security -- making it sound like 3
disjoint
namespaces.  So, how many attrib namespaces are their, 2 or 3?

(3) Adding a bit more to pique my curiosity, I noticed that
file ACL's were in the root-namespace, not the security attribute namespace.
Wouldn't it make more sense if access control was considered a security
attrib?


Another point of confusion was on the attrib manpage where it says:
CAVEATS
       The list option present in the IRIX version of this command is
not sup‐
       ported.  getfattr provides a mechanism to retrieve all of the
attribute
       names.

(4) What does that mean?  i.e.:

when I use attr -l:

> attr -l openssh-6.1p1-hpn13v14.diff.gz
Attribute "DOSATTRIB" has a 56 byte value for openssh-6.1p1-hpn13v14.diff.gz
Attribute "SAMBA_PAI" has a 25 byte value for openssh-6.1p1-hpn13v14.diff.gz

or addint the -q switch with -l:

> attr -ql openssh-6.1p1-hpn13v14.diff.gz
DOSATTRIB
SAMBA_PAI
---
Does "not supported" mean that it is working by accident and may be
removed   ... because....[_________???______]? 

getfattr is suggested as a replacement, but
(5) how can it be used to list the lengths?  and
(6) how can it be used to list the Security or Root namespaces?

Sorry for all the Q's, but it seemed like there were some missing pieces...



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-07-19  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  8:52 Linda Walsh [this message]
2013-07-19 22:39 ` choice of 'namespace' for ACL's Ben Myers

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=51E8FE5F.8030107@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=linux-xfs@oss.sgi.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