bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: "Ondrej Valousek" <ondrej.valousek.xm@renesas.com>,
	"Pádraig Brady" <P@draigbrady.com>
Cc: coreutils@gnu.org, bug-gnulib@gnu.org
Subject: Re: Improve support for ACLs in coreutils (ls & chmod) following the Solaris way
Date: Mon, 16 Jan 2023 21:22:02 +0100	[thread overview]
Message-ID: <8620854.Cn2kBfCCpG@nimes> (raw)
In-Reply-To: <a27eacd0-d085-08a0-c9cd-a44def173b84@draigBrady.com>

Pádraig Brady wrote:
> So as we see there are lots of "additional attributes"
> with dedicated programs to manipulate them.
> What's the big advantage of merging with ls and chmod,
> over the current situation of separate utilities?

In [1] I'm arguing:

  * A feature that has impact on security, and that its users don't
    understand, is a major security problem it itself. If it's too
    easy to misunderstand what effect a specific ACL has, it will cause
    unintended ACLs to be set.

  * Hence efforts should be made that enable the users to understand
    the ACLs that they may set or have set.

  * Most users have no experience with {get,set}facl, {get,set}fattr,
    {ls,ch}attr, only with 'ls' and 'chmod'. Therefore it will be
    easier for them to learn another 'ls' option that to remember three(!)
    other programs getfacl, getfattr, lsattr.

Bruno

[1] https://lists.gnu.org/archive/html/bug-gnulib/2023-01/msg00086.html





  reply	other threads:[~2023-01-16 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 15:03 Improve support for ACLs in coreutils (ls & chmod) following the Solaris way Ondrej Valousek
2023-01-16 17:23 ` Bruno Haible
2023-01-16 19:15 ` Pádraig Brady
2023-01-16 20:22   ` Bruno Haible [this message]
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=8620854.Cn2kBfCCpG@nimes \
    --to=bruno@clisp.org \
    --cc=P@draigbrady.com \
    --cc=bug-gnulib@gnu.org \
    --cc=coreutils@gnu.org \
    --cc=ondrej.valousek.xm@renesas.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).