From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gettext - acl tests - cygwin specific code path
Date: Thu, 23 Aug 2018 02:54:00 -0000 [thread overview]
Message-ID: <2efd98ab-fa5c-8caa-db45-01736b9fdcbd@gmail.com> (raw)
In-Reply-To: <20180822081308.GF3348@calimero.vinschen.de>
On 8/22/2018 4:13 AM, Corinna Vinschen wrote:
> On Aug 21 11:52, 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>
>
> I just tried this and I can not reproduce the result. I used your above
> testcase with fixed chmod invocations. Eventually:
>
> [...]
> $ chmod 605 /tmp/tmpfile0
> $ ls -l /tmp/tmpfile0
> -rw----r-x 1 corinna vinschen 0 Aug 22 09:44 /tmp/tmpfile0
> $ getfacl /tmp/tmpfile0
> # file: /tmp/tmpfile0
> # owner: corinna
> # group: vinschen
> user::rw-
> group::---
> other::r-x
>
> Please retry all steps and add the cacls output after each getfacl
> output. Additionally it might be important to see the permissions
> of your /tmp dir (ls, getfacl and cacls). Mine has the typical
> 01777 perms. For testing I also created tmpfile0 in a directory
> with perms 0755, but the outcome was the same, as above.
>
> Here are my tmpfile0 perms in cacls output, btw., for comparison:
>
> $ cacls C:/cygwin64/tmp/tmpfile0
> C:\cygwin64\tmp\tmpfile0 NULL SID:(DENY)(special access:)
> READ_CONTROL
>
> MYDOMAIN\corinna:(DENY)(special access:)
> FILE_EXECUTE
>
> MYDOMAIN\corinna:(special access:)
> STANDARD_RIGHTS_ALL
> DELETE
> READ_CONTROL
> WRITE_DAC
> WRITE_OWNER
> SYNCHRONIZE
> STANDARD_RIGHTS_REQUIRED
> FILE_GENERIC_READ
> FILE_GENERIC_WRITE
> FILE_READ_DATA
> FILE_WRITE_DATA
> FILE_APPEND_DATA
> FILE_READ_EA
> FILE_WRITE_EA
> FILE_READ_ATTRIBUTES
> FILE_WRITE_ATTRIBUTES
>
> MYDOMAIN\vinschen:(special access:)
> READ_CONTROL
> SYNCHRONIZE
> FILE_READ_ATTRIBUTES
>
> MYDOMAIN\vinschen:(DENY)(special access:)
> FILE_READ_DATA
> FILE_READ_EA
> FILE_EXECUTE
>
> Everyone:R
C:\opt\cygwin64\tmp\tmpfile0 CYGHOST\cygSimple:(special access:)
STANDARD_RIGHTS_ALL
DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
SYNCHRONIZE
STANDARD_RIGHTS_REQUIRED
FILE_GENERIC_READ
FILE_GENERIC_WRITE
FILE_READ_DATA
FILE_WRITE_DATA
FILE_APPEND_DATA
FILE_READ_EA
FILE_WRITE_EA
FILE_READ_ATTRIBUTES
FILE_WRITE_ATTRIBUTES
CYGHOST\cygSimple:(special access:)
READ_CONTROL
SYNCHRONIZE
FILE_GENERIC_READ
FILE_READ_DATA
FILE_READ_EA
FILE_READ_ATTRIBUTES
Everyone:(special access:)
READ_CONTROL
SYNCHRONIZE
FILE_GENERIC_READ
FILE_READ_DATA
FILE_READ_EA
FILE_READ_ATTRIBUTES
--
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-22 13:49 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
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 [this message]
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=2efd98ab-fa5c-8caa-db45-01736b9fdcbd@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).