From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: incompat in cygwin choice of using '+' as domain and user separator.
Date: Thu, 23 Aug 2018 15:59:00 -0000 [thread overview]
Message-ID: <20180823081135.GN3348@calimero.vinschen.de> (raw)
In-Reply-To: <5B7DE56E.6060109@tlinx.org>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
On Aug 22 15:36, L A Walsh wrote:
> Ran in to this trying to use tar to store acls and xattrs:
>
> > tar caf lawbins.tar scripts scripts- bin
> tar: miner.js: Warning: Cannot acl_to_text: Invalid argument
> tar: run-crons.sys: Warning: Cannot acl_to_text: Invalid argument
> tar: smallprof.out: Warning: Cannot acl_to_text: Invalid argument
> tar: tmon.out: Warning: Cannot acl_to_text: Invalid argument
> tar: ubytes_to_utf8.new: Warning: Cannot acl_to_text: Invalid argument
>
> examining one of these:
>
> > find bin -name tmon.out
> bin/tmon.out
>
> > lsacl bin/tmon.out
> [u::rwx,g::rwx,o:r-x,u:Unknown+User:rwx,g:Unknown+Group:rwx,g:Administrators:rwx,g:Bliss\Domain
> Admins:rwx,m:rwx/] bin/tmon.out
lsacl? I don't know this tool. The fact that it prints the unknown
accounts with '+' and the known account with '\' is weird. This
shouldn't happen. It should print all accounts with a '+'. Please use
`getfacl' to examine the ACLs.
>
> I tried tar in an existing dir:
>
> > mkdir test
> > tar caf test.tar test
> > ll test
> total 0
> > cd test
> > tar xaf ../test.tar
> > ll
> total 0
> drwxrwxr-x+ 1 0 Aug 22 15:26 test/
> > lsacl test
> [u::rwx,g::rwx,g:Bliss\lawgroup:rwx,g:Bliss\Domain Admins:rwx,m:rwx,o:r-x/
> u::rwx,g::rwx,g:Bliss\lawgroup:rwx,g:Bliss\Domain Admins:rwx,m:rwx,o:r-x]
> test
>
> With the above and only standard separator chars, no problem
>
> I'm guessing, but '+' is a reserved char that's not permitted in
> acl_to_text...
No, that's a wrong assumption. Think about it. The ACL given to
acl_to_text is the binary form, so it doesn't contain user or group
names, only uids and gids. The usernames are only generated in the
output.
EINVAL from acl_to_text means the incoming acl is invalid. Either it's
so broken that acl_to_text crashes, or it'sa NULL pointer, or it has
less then MIN_ACL_ENTRIES (3) entry, or it has more than MAX_ACL_ENTRIES
(2730) entries, or it doesn't follow the required rules for POSIX ACLs.
I assume the latter is the case here. *Why* this occurs, I can't
tell. I'd need a simple, reproducible testcase for that.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-23 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 8:14 L A Walsh
2018-08-23 14:35 ` cyg Simple
2018-08-23 16:39 ` Corinna Vinschen
2018-08-23 15:59 ` Corinna Vinschen [this message]
2018-08-27 10:50 ` L A Walsh
2018-08-27 13:53 ` Corinna Vinschen
2018-08-27 17:26 ` Corinna Vinschen
2018-08-27 17:27 ` Corinna Vinschen
2018-08-27 22:47 ` Corinna Vinschen
2018-09-04 20:08 ` handling invalid user/groups (was incompat in cygwin choice of using '+' as domain and user separator.) L A Walsh
2018-09-05 8:04 ` Corinna Vinschen
2018-09-06 0:25 ` L A Walsh
2018-09-05 11:35 ` Andrey Repin
2018-09-05 23:57 ` Odd email symptoms (was Re: handling invalid user/groups) L A Walsh
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=20180823081135.GN3348@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).