public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "İsmail Dönmez" <ismail@donmez.ws>
To: cygwin@cygwin.com
Subject: Re: [TESTERS needed] New POSIX permission handling
Date: Sun, 12 Apr 2015 13:21:00 -0000	[thread overview]
Message-ID: <1428844894032-117479.post@n5.nabble.com> (raw)
In-Reply-To: <20150412083532.GM7343@calimero.vinschen.de>

Hi,


Corinna Vinschen-2 wrote
> On Apr 11 10:11, donmez wrote:
>> Hi,
>> 
>> 
>> Corinna Vinschen-2 wrote
>> > Hi folks,
>> > 
>> > 
>> > I just applied a patch I'm working on for quite some time now.  As I
>> > outlined before on this list, the POSIX permission handling has aged
>> > considerably and, for historical reasons, did things differently
>> > dependent on the calling function.  I took the time to reimplement the
>> > core functionality to handle all ACLs as strictly following POSIX ACL
>> > rules as possible.
>> 
>> I tested the updated package and at least quilt and mutt seems to broken
>> by
>> the permission changes:
>> 
>> [~]> quilt new foo
>> cat: /tmp/quilt.mwTVWM: Permission denied
>> Patch patches/foo is now on top
>> 
>> And running mutt results in:
>> 
>> "Error creating temporary file /tmp/mutt-...."
>> 
>> Rolling back to an older snapshot fixes the problem.
> 
> Thanks, but... 
> 
> No offense, but this is not overly helpful.  The problem is to learn
> *why* this happens and how to fix it.  For that I'd need to know what
> your permissions on /tmp look like (ls -l, getfacl, icacls).  Creating
> files in my /tmp (having an old-style ACL) with the following
> permissions works as desired for me:

Hopefully this will shed some more light:

[~]> uname -rm
2.0.0(0.287/5/3) x86_64

[~]> ls -ld /tmp
drwxrwxrwt+ 1 ismail ismail 0 Apr 12 16:13 /tmp

[~]> getfacl /tmp
# file: /tmp
# owner: ismail
# group: ismail
# flags: --t
user::rwx
user:ismail:rwx
group::rwx
mask:rwx
other:rwx
default:user::rwx
default:group::r-x
default:mask:r-x
default:other:r-x

[~]> icacls C:\\cygwin64\\tmp
C:\cygwin64\tmp UX31A\ismail:(F)
        UX31A\ismail:(RX,W)
        Everyone:(RX,W)
        NULL SID:(RD)
        CREATOR OWNER:(OI)(CI)(IO)(F)
        CREATOR GROUP:(OI)(CI)(IO)(RX)
        Everyone:(OI)(CI)(IO)(RX)

       Successfully processed 1 files; Failed processing 0 files

[~]> touch /tmp/foo

[~]> ls -l /tmp/foo
-rw-r--r--+ 1 ismail ismail 0 Apr 12 16:16 /tmp/foo

[~]> getfacl /tmp/foo
# file: /tmp/foo
# owner: ismail
# group: ismail
user::rw-
user:ismail:r-x
group::---
mask:r--
other:r--

[~]> icacls C:\\cygwin64\\tmp\\foo
C:\cygwin64\tmp\foo 
        NULL SID:(DENY)(Rc,S,X,DC)
        UX31A\ismail:(DENY)(S,X)
        UX31A\ismail:(R,W,D,WDAC,WO)
        UX31A\ismail:(RX)
        UX31A\ismail:(DENY)(S,X)
        UX31A\ismail:(RX)
        Everyone:(R)

Successfully processed 1 files; Failed processing 0 files

<brown paper bag> I hope this to be a generic bug, skimmed over one
important details. This is on Win 10 beta build 10049 x64</brown paper bag>.

Thanks!




--
View this message in context: http://cygwin.1069669.n5.nabble.com/TESTERS-needed-New-POSIX-permission-handling-tp117406p117479.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
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

  reply	other threads:[~2015-04-12 13:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 10:07 Corinna Vinschen
2015-04-10 21:13 ` Warren Young
2015-04-11  9:35   ` Corinna Vinschen
2015-04-11  0:00 ` Steven Penny
2015-04-11  9:40   ` Corinna Vinschen
2015-04-11 10:07     ` Corinna Vinschen
2015-04-11 16:26       ` Ernie Rael
2015-04-12  8:22         ` Corinna Vinschen
2015-04-11 10:23     ` Corinna Vinschen
2015-04-11 10:47     ` Steven Penny
2015-04-11 14:30       ` Corinna Vinschen
2015-04-11 16:05       ` Andrey Repin
2015-04-12 17:37         ` Adam Dinwoodie
2015-05-16  2:39   ` Steven Penny
2015-05-17  7:44     ` Duncan Roe
2015-05-19  7:52     ` Jiří Engelthaler
2015-04-11  8:47 ` Achim Gratz
2015-04-11  9:02   ` David Macek
2015-04-11  9:08     ` Achim Gratz
2015-04-11  9:51       ` David Macek
2015-04-11 11:51         ` Achim Gratz
2015-04-11 10:00     ` Corinna Vinschen
2015-04-11 12:36       ` David Macek
2015-04-11 14:31         ` Corinna Vinschen
2015-04-11  9:44   ` Corinna Vinschen
2015-04-11 11:11     ` Bryan Berns
2015-04-11 14:32       ` Corinna Vinschen
2015-04-11 16:05   ` Andrey Repin
2015-04-11 17:11 ` donmez
2015-04-12  8:35   ` Corinna Vinschen
2015-04-12 13:21     ` İsmail Dönmez [this message]
2015-04-12 14:25       ` Corinna Vinschen
2015-04-15 15:42         ` Corinna Vinschen
2015-04-16 10:20           ` Ismail Donmez
2015-04-16 11:03             ` Corinna Vinschen
2015-04-16 16:09               ` Ismail Donmez
2015-04-16 16:24                 ` Corinna Vinschen
2015-04-16 16:48                   ` Ismail Donmez
2015-04-17  7:30                     ` Corinna Vinschen
2015-04-17 10:06                       ` Corinna Vinschen
2015-04-17 15:17                         ` Ismail Donmez
2015-04-17 16:22                           ` 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=1428844894032-117479.post@n5.nabble.com \
    --to=ismail@donmez.ws \
    --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).