X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=poysgj6xz9uRVbmlpNfsSzd/peEfoqvXQKq95ZWYmCs
	Ts0TUtPxxJQubqNz2ZEf7gI2ij++ISCJiuOYAZuqAxXhCc/YnWE9dwOb1IlSfuFg
	q32BAOGF96lW5Sybk5b0wP9vVINkX6fP6lDXQKi3ZegspHqZKZTGMkBMC4JboPwQ
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=RWpJU5rlvL0vU4my8WlDkP0C8lM=; b=ClQLaF1eNLp5PgWmS
	3napburiGPJL3UAW30oAx2lgT/hT8f6dovbGVTHIhOQW1QC1BFVmvdfmVlXx0JmG
	h0aNkvp4GtI/8tlNLmBe+Sl+ORjC/MskkFD9GxWb8P7QmTh0BNXuBP8+e0b3lEE4
	DgDLNrWIfmfUa6qkYxcJjSEl48=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: Ishtar.hs.tlinx.org
Message-ID: <5511C913.8020006@tlinx.org>
Date: Tue, 24 Mar 2015 13:29:07 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com, cygwin AT cygwin DOT com
Subject: Re: mkpasswd: option to force the 'primary' domain?
References: <550C0B53 DOT 6080201 AT thales-esecurity DOT com> <20150320181011 DOT GB12906 AT calimero DOT vinschen DOT de>
In-Reply-To: <20150320181011.GB12906@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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