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=Pf0tsR8hq+3sXCrozAlAdIMG0DVeqpgK5/fUFjoPbfu
	7ZvZuu/6vWjfjbLM3K6wWqLnVB9c7Vj42ebHFdbiUEhPALEJeYLZCaW9PuhD5+Xg
	g4gQUUcSBXynG+OZFAsP3Pe9NvKstj+YFW9WmqGQ1ghyxpUhSllmMZoMVERoi8Jc
	=
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=9rRq7vy/xj+d1PjOg4LEjGMrhkQ=; b=LcxY+36mBQyeG8jQa
	bC0ekpEtsqOOuNKsXc7V5qtsi7IAmFMeYJoedJA6ZmPAtswxPsRmCOthldL4qs6I
	BbZkO53EfQAAMNJgUWttUBYKsb0rw6vGrip4LB9IfbaCRvsF4DvhHxx83eEcIGzN
	PkZBEAnB7ZRB5kb+cTVkYHEt9k=
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=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	mailout09.t-online.de
Message-ID:	<545BD14A.8080803@t-online.de>
Date:	Thu, 06 Nov 2014 20:51:38 +0100
From:	Christian Franke <Christian DOT Franke AT t-online DOT de>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
References:	<announce DOT 20141105164319 DOT GA31314 AT calimero DOT vinschen DOT de> <545B17B8 DOT 5010509 AT t-online DOT de> <20141106164915 DOT GG28195 AT calimero DOT vinschen DOT de> <545BBF4B DOT 4020400 AT t-online DOT de> <20141106185019 DOT GK28195 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20141106185019.GK28195@calimero.vinschen.de>
X-IsSubscribed:	yes

Corinna Vinschen wrote:
> On Nov  6 19:34, Christian Franke wrote:
>> Corinna Vinschen wrote:
>>> On Nov  6 07:39, Christian Franke wrote:
>>>> Corinna Vinschen wrote:
>>>>> Hi Cygwin friends and users,
>>>>>
>>>>>
>>>>> I just released a 6th TEST version of the next upcoming Cygwin release,
>>>>> 1.7.33-0.6.
>>>>>
>>>> Looks good so far.
>>>>
>>>> An observation from my first test on a machine which is member of a domain:
>>>>
>>>> mkpasswd -l and -L always print the HOST prefix.
>>>> mkpasswd -d and -D never print the DOMAIN prefix
>>> Right.  That's by design.  -D is deprecated.  -L of the new mkpasswd/
>>> mkgroup (which hopefully are not used by users a lot in future) only
>>> prefix *foreign* machines.
>> But why does
>>    mkpasswd -l (no host) -- adds a prefix
>>    mkpasswd -l THISHOST -- does not add a prefix
>> when the machine is in a domain? Not consistent, IMO.
> That's right.  The reason is that the machine name is treated as a
> foreign machine.  In theory, this should always generate names
> with prefixed machine name, but this is an entirely different
> code path in mkpasswd/mkgroup.  I guess this should be fixed.
>
> I wouldn't be unhappy about help...

I would only fix it back to the old behaviour (mkpasswd -l = no prefix), 
sorry :-)

At my real job we run several build & test machines which are members of 
a domain but use various local test user accounts (with no collision 
with domain users due to name space rules). Loosing the ability to use 
prefix-less local user names would break various existing test scripts 
(which are also used on Linux).

Generated emails would have a from address with HOST+USER name part 
which might give interesting results if the mail system somehow 
interprets the NAME+EXTENSION address syntax...

So there are use cases where prefix-less local user names are needed. 
This should be still supported, e.g. by mkpasswd -l, IMO.


>
>>
>> But PLEASE keep the ability to create local users/groups without a prefix.
>> Otherwise useful configuration defaults (mail_owner=postfix, ...) would be
>> no longer useful because config files must be tweaked for each host
>> (mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such
>> technical users (sshd?) might also be hard coded or a config parser might
>> not like the HOST+USER syntax.
> And how's that supposed to work?  Even if we introduce a way in
> /etc/nsswitch.conf to generate usernames differently, it doesn't really
> help.  Your config file should be able to work with default settings
> and not force the admin to use specific settings in nsswitch.conf.

The 'PLEASE keep ...' was only related to the new csih script. It should 
be able to optionally put prefix-less local usernames to /etc/passwd.

Christian


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

- Raw text -