public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: RFC2307 accounts
Date: Wed, 09 Mar 2016 15:58:00 -0000	[thread overview]
Message-ID: <20160309155843.GA32399@calimero.vinschen.de> (raw)
In-Reply-To: <56E00DF7.7060406@studelec-sa.com>

[-- Attachment #1: Type: text/plain, Size: 2349 bytes --]

On Mar  9 12:50, Marc Rechte wrote:
> Le 09/03/2016 12:27, Corinna Vinschen a écrit :
> >Keep in mind that we have two mappings.  The main mapping is the mapping
> >between Windows SID and a computed uid/gid value used in Cygwin which
> >allows fast mapping in both directions.  A computed value drops the
> >requirement to access an LDAP server for the mapping, which is
> >especially bad when not using AD as mapping server.
> >
> >Please read https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nfs
> >and https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-samba
> >again.  The RFC 2307 mapping only comes into play when reading meta
> >information from an NFS or Samba share.  The unix uid/gid values have to
> >be mapped to a Windows user (better: SID) in the first place, not to the
> >Cygwin uid/gid values.  The actual uid/gid values are irrelevant.  Worse,
> >using the RFC 2307 values might collide with other, computed uid/gid
> >values.
> >
> >
> >Corinna
> >
> 
> OK, I noticed that. Now it brings me a problem using rsync on cygwin.
> 
> On cygwin:
> $ cat /etc/rsyncd.conf
> [test]
>         path = /cygdrive/c/tmp
>         comment = zone de test
>         fake super = yes
>         read only = no
> 
> On the Linux box:
> # ls -l /home/tunix/
> ...
> drwxr-xr-x  3 tunix root                     4096  9 mars  12:23 resto_win
> -rw-rw-r--+ 1 tunix utilisateurs_du_domaine 82882  9 mars  10:56 tmp.ps
> 
> #  rsync -avz --acls --delete /home rsync://192.168.0.23/test
> ..
> # rsync -avz --acls --delete rsync://192.168.0.23/test/home/tunix resto_win/
> ...
> # ls -l /home/tunix/resto_win/tunix/
> ...
> drwx------ 2 1050005 1049089  4096  9 mars  12:14 resto_win
> -rw------- 1 1050005 1049089 82882  9 mars  10:56 tmp.ps

That's an ls -ln, right?  The AD user and group names should have been
resolved.

> You will notice that owner, group and ACLs  are *not* restored properly
> 
> Am I demanding too much to cygwin ?

Off the top of my head, yes.  The rfc2307 uid/gid mapping only works
when accessing the filesystem directly from Cygwin.  By using rsync, the
info is transmitted over the net.


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: 819 bytes --]

  reply	other threads:[~2016-03-09 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  7:09 Marc Rechte
2016-03-09  9:14 ` Mark Geisert
2016-03-09 10:43   ` Marc Rechte
2016-03-09 11:28     ` Corinna Vinschen
2016-03-09 11:50       ` Marc Rechte
2016-03-09 15:58         ` Corinna Vinschen [this message]
2016-03-09 16:08           ` Marc Rechte
2016-03-09 22:05         ` Andrey Repin
  -- strict thread matches above, loose matches on Subject: below --
2016-03-08 16:30 Marc Rechte
2016-03-08 17:00 ` 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=20160309155843.GA32399@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).