From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: mkpasswd: option to force the 'primary' domain?
Date: Wed, 25 Mar 2015 00:50:00 -0000 [thread overview]
Message-ID: <20150324212838.GA3017@calimero.vinschen.de> (raw)
In-Reply-To: <5511C913.8020006@tlinx.org>
[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]
On Mar 24 13:29, Linda Walsh wrote:
> Corinna Vinschen wrote:
> >On Mar 20 11:58, Tim Magee wrote:
> >>Now then,
> >>
> >>Since Cygwin 1.7.34 dropped, mkpasswd has been problematic for us. Our
> >>problem is with the way user names pulled from outside the primary domain
> >>get decorated. My question is: will there ever be a way to tell
> >>mkpasswd/mkgroup "make <some non-primary domain> the one whose users get
> >>undecorated names"?
> ----
> >I'm not planning this. The idea is that mkpasswd/mkgroup create account
> >names compatible with the "db"-based accounts and everyhing else is left
> >to post-creation manipulation.
> ---
> I never quite managed to understand this -- as my pw/grp files on
> my client machines were already in sync with my domain setup and
> worked as it would in a real Win Domain (i.e. Domain applied when I signed
> into a machine that wasn't the domain controller and was using domain
> credentials). If I logged into a machine with a local account, there has never
> been a domain name to have to bother with -- so for me user-logins were prefixed
> with the domain only when they were in a domain.
>
> This has been the way windows has worked for as long as I've run a domain server --
> if a local machine is not in a domain, then it's username-only, but if it is
> in a domain, then I'd need to type-or-add the local-machine name to NOT login
> via the domain creds.
>
> For local accounts, the RID==the UID, for domain accounts the RID==the UID on
> the domain controller.
>
> Do I understand that cygwin is no longer compatible with window's (and
> samba's) naming convention? That would be a pain.
Did you go to the trouble to read the new documentation under
https://cygwin.com/cygwin-ug-net/ntsec.html? It's all explained there.
If you don't like it, use passwd and group files with changed user names.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-24 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 12:24 Tim Magee
2015-03-20 18:11 ` Corinna Vinschen
2015-03-24 12:40 ` Tim Magee
2015-03-24 20:34 ` Linda Walsh
2015-03-25 0:50 ` Corinna Vinschen [this message]
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=20150324212838.GA3017@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).