From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: Cygwin 3.5 mapping uid/gid on NFSv4 filesystem to unexpected IDs ...
Date: Mon, 13 Nov 2023 20:39:17 +0100 [thread overview]
Message-ID: <ZVJ7ZU3BtsoJutJd@calimero.vinschen.de> (raw)
In-Reply-To: <CAKAoaQki+KcY6=rDnzWMrxFomXnJpoLD97Xj+XO2BLJ8AdU-Yw@mail.gmail.com>
On Nov 10 13:22, Roland Mainz wrote:
> On Tue, Oct 31, 2023 at 5:20 PM Roland Mainz <roland.mainz@nrubsig.org> wrote:
> >
> > Is the Cygwin behaviour (i.e. mapping of NFS3Attr uid/gid to different
> > uid/gid in Cygwin $ ls -n #) intended ?
>
> In the meantime I tried this:
> ---- snip ----
> # Map NFSv4 uid/gid 1:1 to Cygwin uid/gid - does not work
> regtool -i set '/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NTDS/trustPosixOffset'
> 0x0
> regtool -i set '/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Netlogon/Parameters/trustPosixOffset'
> 0x0
> ---- snip ----
This can't work. trustPosixOffset is not a value in the registry. It's
stored in AD only and fetched from the domain's system container via
LDAP.
uid/gid mapping between NFS server and Cygwin works by utilizing the NFS
client's identity mapping as described in
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nfs
If this doesn't fit your needs, you have to overload what's given to you
by maintaining this info via /etc/passwd and /etc/group entries.
Corinna
next prev parent reply other threads:[~2023-11-13 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:20 Roland Mainz
2023-11-10 12:22 ` Roland Mainz
2023-11-13 19:39 ` Corinna Vinschen [this message]
2023-11-13 20:41 ` Roland Mainz
2023-11-15 12:57 ` Corinna Vinschen
2023-11-15 14:40 ` Corinna Vinschen
2023-11-13 22:52 ` Cedric Blancher
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=ZVJ7ZU3BtsoJutJd@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@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).