From: Liam Gretton <liam.gretton@leicester.ac.uk>
To: linux-nfs@vger.kernel.org
Subject: [PATCH] nfs4-acl-tools (spaces in principal names)
Date: Wed, 18 Jul 2012 22:46:31 +0100 [thread overview]
Message-ID: <50072EB7.9030402@leicester.ac.uk> (raw)
In-Reply-To: <50072D57.4060903@leicester.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
Attached is a patch which changes the behaviour of nfs4_setfacl slightly
to allow it to add, remove and modify ACLs which act on principals
containing space characters.
The rationale behind this is to allow us to use nfs4_setfacl on a file
system which is shared via CIFS to Windows clients and NFSv4. Though
very rare in a Unix environment, Windows commonly uses user names (and
hence principals derived from them) which contain spaces. A particularly
common one is 'Domain Admins', the handling of which prompted me to look
at modifying the nfs4_setfacl command.
As of 0.3.3 of nfs4-acl-tools, nfs4_setfacl fails to handle ACLs
containing a space character no matter what attempts to quote the ACE or
escape the space character:
# nfs4_setfacl -a "A:fdg:Domain Admins@dom.org:R" file
Scanning ACE string 'A:fdg:Domain' failed.
Failed while inserting ACE(s) (at index 1).
(exit status 1.)
# nfs4_setfacl -a A:fdg:Domain\ Admins@dom.org:R file
Scanning ACE string 'A:fdg:Domain' failed.
Failed while inserting ACE(s) (at index 1).
(exit status 1.)
The attached patch modifies the parsing of the command line and
disallows space as an ACE delimiter. The patched version completes
successfully:
# nfs4_setfacl -a "A:fdg:Domain Admins@dom.org:R" file
# nfs4_getfacl file
A:fdg:Domain Admins@le.ac.uk:rtncy
ACEs can be chained with commas, but no longer with spaces. With the -A,
-X, -S or -e options which expect a file containing ACLs, ACEs can be
separated with tabs, newlines and/or carriage returns as before.
As there's a slight change in behaviour, the patch also modifies one of
the examples given in the EXAMPLES section of nfs4_setfacl(1) and the
text of the 'ACL FORMAT' section of nfs4_acl.
The patches don't modify any version numbers or dates.
Regards,
Liam
--
Liam Gretton liam.gretton@le.ac.uk
HPC Architect http://www.le.ac.uk/its/
IT Services Tel: +44 (0)116 2522254
University Of Leicester, University Road
Leicestershire LE1 7RH, United Kingdom
[-- Attachment #2: nfs4-acl-tools.patch --]
[-- Type: text/plain, Size: 1790 bytes --]
diff -rup b_nfs4-acl-tools/libnfs4acl/nfs4_insert_string_aces.c a_nfs4-acl-tools/libnfs4acl/nfs4_insert_string_aces.c
--- b_nfs4-acl-tools/libnfs4acl/nfs4_insert_string_aces.c 2012-07-18 21:14:47.000000000 +0100
+++ a_nfs4-acl-tools/libnfs4acl/nfs4_insert_string_aces.c 2012-07-18 11:51:43.000000000 +0100
@@ -45,7 +45,7 @@ int nfs4_insert_string_aces(struct nfs4_
if ((s = sp = strdup(acl_spec)) == NULL)
goto out_failed;
- while ((ssp = strsep(&sp, " ,\t\n\r")) != NULL) {
+ while ((ssp = strsep(&sp, ",\t\n\r")) != NULL) {
if (!strlen(ssp))
continue;
diff -rup b_nfs4-acl-tools/man/man1/nfs4_setfacl.1 a_nfs4-acl-tools/man/man1/nfs4_setfacl.1
--- b_nfs4-acl-tools/man/man1/nfs4_setfacl.1 2012-07-18 21:14:47.000000000 +0100
+++ a_nfs4-acl-tools/man/man1/nfs4_setfacl.1 2012-07-18 21:13:02.000000000 +0100
@@ -204,7 +204,7 @@ delete the first ACE, but only print the
.IP - 2
delete the last two ACEs above:
.br
- $ nfs4_setfacl -x "A::EVERYONE@rtncy, D::EVERYONE@:waxTC" foo
+ $ nfs4_setfacl -x A::EVERYONE@rtncy,D::EVERYONE@:waxTC foo
.IP - 2
modify (in-place) the second ACE above:
.br
diff -rup b_nfs4-acl-tools/man/man5/nfs4_acl.5 a_nfs4-acl-tools/man/man5/nfs4_acl.5
--- b_nfs4-acl-tools/man/man5/nfs4_acl.5 2012-07-18 21:14:47.000000000 +0100
+++ a_nfs4-acl-tools/man/man5/nfs4_acl.5 2012-07-18 21:11:11.000000000 +0100
@@ -56,7 +56,7 @@ more permissive than the ones you set.
.SH ACL FORMAT
An NFSv4 ACL is written as an
.IR acl_spec ,
-which is a comma- or whitespace-delimited string consisting of one or more
+which is a comma- or tab-delimited string consisting of one or more
.IR ace_specs .
A single NFSv4 ACE is written as an
.IR ace_spec ,
next parent reply other threads:[~2012-07-18 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50072C9E.7080707@leicester.ac.uk>
[not found] ` <50072D57.4060903@leicester.ac.uk>
2012-07-18 21:46 ` Liam Gretton [this message]
2012-07-18 23:41 ` [PATCH] nfs4-acl-tools (spaces in principal names) Bruce Fields
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=50072EB7.9030402@leicester.ac.uk \
--to=liam.gretton@leicester.ac.uk \
--cc=linux-nfs@vger.kernel.org \
/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.