From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gettext - acl tests - cygwin specific code path
Date: Tue, 21 Aug 2018 23:57:00 -0000 [thread overview]
Message-ID: <05c3ca13-c103-ae7d-e727-a995a4cf5f66@gmail.com> (raw)
In-Reply-To: <20968a92-9900-5fd0-807c-29facf8b84de@gmail.com>
On 8/21/2018 11:52 AM, cyg Simple wrote:
> I've been reviewing the testing of gettext and I have a failure for all
> of the acl tests. I've found that a file without acl will obtain acl if
> the mode is changed to 605. STC below.
>
> <STC>
> $ touch /tmp/tmpfile0
> $ ls -l /tmp/tmpfile0
> -rw-r--r-- 1 myUser myGroup 0 Aug 21 11:35 /tmp/tmpfile0
> $ getfacl /tmp/tmpfile0
> # file: /tmp/tmpfile0
> # owner: myUser
> # group: myGroup
> user::rw-
> group::r--
> other:r--
> $ chmod 600
> $ ls -l /tmp/tmpfile0
> -rw------- 1 myUser myGroup 0 Aug 21 11:35 /tmp/tmpfile0
> $ getfacl /tmp/tmpfile0
> # file: /tmp/tmpfile0
> # owner: myUser
> # group: myGroup
> user::rw-
> group::---
> other:---
> $ chmod 605
> $ ls -l /tmp/tmpfile0
> -rw----r-x+ 1 myUser myGroup 0 Aug 21 11:35 /tmp/tmpfile0
> $ getfacl /tmp/tmpfile0
> # file: /tmp/tmpfile0
> # owner: myUser
> # group: myGroup
> user::rw-
> group::---
> other:r-x
> user:myUser:---
> </STC>
>
> gettext loops through a number of modes and fortunately one of those had
> an owner and other without the group. Anytime the other is set without
> the owner or group having permission we get an ACL for the user which is
> wrong. A `setfacl -b /tmp/tmpfile0` doesn't correct the information
> from getfacl.
>
During the testing at least one of the tests does `setfacl -m group:0:1
tmpfile0`. Obviously this gets a 'permission denied' error as group 0
doesn't exist. What do you suggest for reasonable replacement for 0?
I'm thinking 11(Authenticated Users) as the purpose of the test is to
determine if the use of `set_acl (file, -1, mode);` will reset to a file
without acl.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-08-21 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 20:53 cyg Simple
2018-08-21 23:57 ` cyg Simple [this message]
2018-08-22 8:13 ` Marco Atzeri
2018-08-22 8:16 ` Andrey Repin
2018-08-22 10:19 ` cyg Simple
2018-08-22 13:37 ` Corinna Vinschen
2018-08-22 22:36 ` cyg Simple
2018-08-22 13:49 ` Andrey Repin
2018-08-22 10:24 ` Corinna Vinschen
2018-08-23 2:54 ` cyg Simple
2018-08-23 23:13 ` Corinna Vinschen
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=05c3ca13-c103-ae7d-e727-a995a4cf5f66@gmail.com \
--to=cygsimple@gmail.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).