From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: RFC2307 accounts
Date: Wed, 09 Mar 2016 11:28:00 -0000 [thread overview]
Message-ID: <20160309112750.GA14733@calimero.vinschen.de> (raw)
In-Reply-To: <56DFFE26.9080705@studelec-sa.com>
[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]
On Mar 9 11:42, Marc Rechte wrote:
> Le 09/03/2016 10:14, Mark Geisert a écrit :
> >Marc Rechte wrote:
> >>Hello,
> >>
> >> Trying to set RFC2307 accounts, using unix schema in
> >>/etc/nsswitch.conf.
> >[...]
> >
> >Your original post of this material was answered about 30 minutes after
> >your post. Kindly follow up there...
> >
> >https://cygwin.com/ml/cygwin/2016-03/msg00076.html
> Sorry, I did not get that answer emailed to me (some confusion during the
> subscription).
>
> I am not clear with answer given by Corinna.
>
> The idea behind RFC2307, imho is to have a consistent UID/GID between
> systems which have joined a domain. This is what we achieved in our domain,
> where a user login into whatever Linux box, gets the same uid/gid. One would
> expect the same behaviour in cygwin (on a joined machine), wouldn't he ?
That's not the idea behind the uid/gid mapping. You might have noticed
that "unix" is not used as a keyword in the passwd and group settings
in /etc/nsswitch.conf, only in the db_home, db_shell, and db_gecos settings.
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
--
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 --]
next prev parent reply other threads:[~2016-03-09 11:28 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 [this message]
2016-03-09 11:50 ` Marc Rechte
2016-03-09 15:58 ` Corinna Vinschen
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=20160309112750.GA14733@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).