From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-3
Date: Tue, 14 Apr 2015 08:58:00 -0000 [thread overview]
Message-ID: <20150414085757.GC7343@calimero.vinschen.de> (raw)
In-Reply-To: <2bbd046b7e2ea40818416d8a6d3f15b8.squirrel@webmail.xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]
On Apr 13 18:10, Houder wrote:
> Hi Corinna,
>
> Perhaps not relevant anymore (since you have returned to the drawing board) ...
>
> - after installing update 3 to Cygwin 2.0 ...
> - created file while being logged on as user Test; subsequently executed: chmod 460 file
> - switched back to user Henri and attempted to touch file: failed
> - however, using Cygwin 1.7, and repeating the same procedure, I am able to touch the file (called file2)
>
> Regards,
>
> Henri
>
> = Cygwin 2.0 -- logged on as user Test
>
> %% uname -a
> CYGWIN_NT-6.1-WOW Seven 2.0.0(0.287/5/3) 2015-04-12 21:09 i686 Cygwin
> %% pwd
> /home/Test
> %% id
> uid=197614(Test) gid=197121(None) groups=197121(None), ... followed by irrelevant j.
> 545(Users), 4(INTERACTIVE)66049(CONSOLE LOGON),11(Authenticated Users),15(This Organization),113(Local
> acount),4095(CurrentSession),
> 66048(LOCAL),262154(NTLM Authentication),401408(Medim Mandatory Level)
> %% touch file
> %% chmod 460 file
> %% echo aha > file
> bash: file: Permission denied
>
> %% getfacl file
> # file: file
> # owner: Test
> # group: None
> user::r--
> group::r-x
> mask:rw-
Huh? So it creates a mask even though it only contains standard POSIX
permissions. This explains the "permission denied". The group r-x
combined with a mask rw- results in effective r-- permissions for the
group None. This yet again calls for adding the output of effective
permissions to getacl.
I think I fixed the thinko in the code. At one point I noticed that I
mishandled the GROUP_OBJ permssions in new-style ACEs and my fix was
apparently a bit too efficient :}
I uploaded new snapshots to https://cygwin.com/snapshots/ and I'm just
uploading a 2.0.0-0.4 release.
Please give either of them a try.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-14 8:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 16:10 Houder
2015-04-14 8:58 ` Corinna Vinschen [this message]
2015-04-14 14:18 ` Houder
2015-04-14 14:50 ` Corinna Vinschen
2015-04-14 15:01 ` Houder
2015-04-14 15:12 ` Corinna Vinschen
2015-04-14 15:26 ` Houder
2015-04-14 15:45 ` Corinna Vinschen
2015-04-14 16:32 ` Houder
2015-04-14 18:21 ` Corinna Vinschen
2015-04-14 18:38 ` Houder
2015-04-15 7:13 ` Corinna Vinschen
2015-04-15 7:46 ` Houder
2015-04-15 9:04 ` Corinna Vinschen
2015-04-14 14:27 ` Achim Gratz
2015-04-14 14:52 ` Corinna Vinschen
2015-04-14 15:35 ` Achim Gratz
2015-04-14 15:53 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2015-04-12 19:23 Corinna Vinschen
2015-04-12 21:19 ` Bryan Berns
2015-04-13 7:17 ` Corinna Vinschen
2015-04-13 7:32 ` Corinna Vinschen
2015-04-13 11:13 ` Bryan Berns
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=20150414085757.GC7343@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).