From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [Bug] File permissions across domains
Date: Wed, 11 Apr 2018 09:35:00 -0000 [thread overview]
Message-ID: <20180411093443.GM29703@calimero.vinschen.de> (raw)
In-Reply-To: <20180411070312.GK29703@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
On Apr 11 09:03, Corinna Vinschen wrote:
> Same here, belong on the Cygwin ML. Redirecting.
>
> Corinna
>
> On Apr 10 18:47, Achim Gratz wrote:
> >
> > We're in the midst of switching to a different LDAP domain
> > organisation. All my accounts still arein the old domain and that leads
> > to problems when lookking at shares from a mchine in the new domain:
> >
> > --8<---------------cut here---------------start------------->8---
> > (1027)/mnt/upload > touch bla
> > (1027)/mnt/upload > getfacl bla
> > # file: bla
> > # owner: OLD+gratz
> > # group: OLD+Domain Users
> > user::---
> > group::---
> > group:OLD+cygwinupload:rwx
> > mask:rwx
> > other:---
> >
> > (1028)/mnt/upload > ls -l bla
> > ----rwx---+ 1 OLD+gratz OLD+Domain Users 0 Apr 10 14:41 bla
> > --8<---------------cut here---------------end--------------->8---
> >
> > So Cygwin correctly figures that I'm the owner of the file, but fails to
> > translate my access rights (via group OLD+cygwinupload) into the owner
> > part of the modes like it does when I look at the same file from a
> > machine in the old domain. That in turn confuse sprograms that check
> > the modes before the ACL (like Git) to tell me that I can't access the
> > files (or that there is no repository in the case of Git).
This is a bit low on detail. What does icacls say about this file? How
does getfacl report the ACL on a machine in the old domain? What does
ls -l report on the file on both machines? Does an strace on getfacl
report an error in ACL checking?
Thanks,
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-04-11 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874lkjt3dw.fsf@Rainer.invalid>
2018-04-11 7:03 ` Corinna Vinschen
2018-04-11 9:35 ` Corinna Vinschen [this message]
2018-04-11 17:17 ` Achim Gratz
2018-04-12 7:38 ` Corinna Vinschen
2018-04-12 7:56 ` Csaba Raduly
2018-04-12 10:13 ` Corinna Vinschen
2018-04-12 19:16 ` Achim Gratz
2018-04-13 12:30 ` Corinna Vinschen
2018-04-13 19:31 ` Achim Gratz
2018-04-22 7:25 ` Achim Gratz
2018-04-23 8:54 ` 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=20180411093443.GM29703@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).