From: Ondrej Valousek <ondrej.valousek.xm@renesas.com>
To: "coreutils@gnu.org" <coreutils@gnu.org>
Cc: "bug-gnulib@gnu.org" <bug-gnulib@gnu.org>
Subject: Improve support for ACLs in coreutils (ls & chmod) following the Solaris way
Date: Mon, 16 Jan 2023 15:03:51 +0000 [thread overview]
Message-ID: <TYXPR01MB18540C286CF6C3CFBD75D4CDD9C19@TYXPR01MB1854.jpnprd01.prod.outlook.com> (raw)
Hi,
As per our conversation with Bruno I was thinking if it would make a sense to extend support of ACLs in gnulib/coreutils, mainly covering "ls" (1st stage) and "chmod" (2nd stage) with the goal to have the ACLs better understandable for end users.
For "ls" we would:
- Introduce a new flag "-V" that would work like "-l" but also append text interpretation of ACLs as in Solaris, i.e.:
# ls -V
total 7
-rw-r--r--+ 1 root root 5 Jan 4 09:11 acl
user:ondrej:rwx-----------:-------:allow
owner@:rw-p--aARWcCos:-------:allow
group@:r-----a-R-c--s:-------:allow
everyone@:r-----a-R-c--s:-------:allow
For "chmod" we would add new option "A" that would allow modify ACEs like in Solaris:
# chmod A+user:marks:rw- file.1
Technical implementation:
- I'd like to support NFSv4 ACLs, but since we have no library for it, then we would need to provide some parsing code for it and stick in Gnulib - we have something in "file-has-acl.c" already and it would be a good starting point.
- file_has_acl() function would need to be modified slightly to return 2 in case NFSv4 acls were found (this is backward compatible).
For Posix acls we would use the existing libacl.
Is this something I would find support in both coreutils and Gnulib?
Thanks
Ondrej
next reply other threads:[~2023-01-16 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 15:03 Ondrej Valousek [this message]
2023-01-16 17:23 ` Improve support for ACLs in coreutils (ls & chmod) following the Solaris way Bruno Haible
2023-01-16 19:15 ` Pádraig Brady
2023-01-16 20:22 ` Bruno Haible
2023-01-17 23:28 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TYXPR01MB18540C286CF6C3CFBD75D4CDD9C19@TYXPR01MB1854.jpnprd01.prod.outlook.com \
--to=ondrej.valousek.xm@renesas.com \
--cc=bug-gnulib@gnu.org \
--cc=coreutils@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).