public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [Bug] File permissions across domains
Date: Wed, 11 Apr 2018 17:17:00 -0000	[thread overview]
Message-ID: <87r2nlwtln.fsf@Rainer.invalid> (raw)
In-Reply-To: <20180411093443.GM29703@calimero.vinschen.de> (Corinna Vinschen's	message of "Wed, 11 Apr 2018 11:34:43 +0200")

Corinna Vinschen writes:
> 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?

There is absolutely no error when stracing getfacl on either machine.
From the machine in the new domain (my account is in group cygwinupload
and access on this share is via ACL only, I can't change ACL):

--8<---------------cut here---------------start------------->8---
/mnt/upload > ll bla
----rwx---+ 1 OLD+gratz OLD+Domain Users 0 Apr 10 15:21 bla
(1011)/mnt/upload > getfacl bla
# file: bla
# owner: OLD+gratz
# group: OLD+Domain Users
user::---
group::---
group:OLD+FileOperators:rwx
group:OLD+cygwinupload:rwx
mask:rwx
other:---

(1012)/mnt/upload > `cygpath -S`/icacls bla
bla OLD\FileOperators:(I)(F)
    OLD\cygwinupload:(I)(M)

Successfully processed 1 files; Failed processing 0 files
--8<---------------cut here---------------end--------------->8---

The same thing on a machine in the old domain:

--8<---------------cut here---------------start------------->8---
(1007)/mnt/upload > ll bla
-rwxrwx---+ 1 gratz Domain Users 0 Apr 10 15:21 bla
(1008)/mnt/upload > getfacl bla
# file: bla
# owner: gratz
# group: Domain Users
user::rwx
group::---
group:FileOperators:rwx
group:cygwinupload:rwx
mask:rwx
other:---

(1009)/mnt/upload > `cygpath -S`/icacls bla
bla OLD\FileOperators:(I)(F)
    OLD\cygwinupload:(I)(M)

Successfully processed 1 files; Failed processing 0 files
--8<---------------cut here---------------end--------------->8---

Checking how Cygwin reads my own account results in exactly the same SID
on both machines as it should, but of course Cygwin translates that to
different uid / gid values due to the presence of the domain prefix when
I'm logged into the machine in the new domain:

OLD+gratz:*:2147559089:2147484161:U-OLD\gratz,S-1-5-21-20…441:/home/gratz:/bin/bash
gratz:*:1124017:1049089:U-OLD\gratz,S-1-5-21-20…441:/home/gratz:/bin/bash

I have not yet tried to force the account back to a prefix-less
interpretation via /etc/passwd (I had to do that in my home network
without a DC to solve a similar problem, but I'd like to avoid that
here).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

--
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:[~2018-04-11 17:17 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
2018-04-11 17:17     ` Achim Gratz [this message]
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=87r2nlwtln.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).