Re: mkpasswd: option to force the 'primary' domain?

[Linda Walsh <cygwin at tlinx dot org>]

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.





--
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