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=hHSZAb3G54U4d0Re1FF/i3+KgJXbtj7YE/B2QXgZwXc
	4DJIse24LwY+7kRSLkGyikuYKICdUMCIcq5BLIMBccYjUN+QbTEDRYSUHIjRLiGJ
	tKQPAtz+invPUJO4FlPlNmOqz+GttfsB8zwOxx6/jGlWhsW/sDqO+TBcDJrZG9uk
	=
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=7HzFqiStsWzF1hRYkgwr+hnXyTU=; b=wtnsDEgY331IWOf1M
	tg6Ki+dt32t9lSTfK2U3xHgygz5CPoR7agWZw+lR9USqg71tSeA60IZC8Q6srb9B
	fnxKTN4Iw4HX+VeZitcF42tk9Rgr6hLTRHIYawLNkIKviuffy+EfCAQ115egLPyQ
	UJT+uKvg/0hlOgALdOPl99s7Ts=
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:	<54611048.4000404@t-online.de>
Date:	Mon, 10 Nov 2014 20:21:44 +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:	<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> <545BD14A DOT 8080803 AT t-online DOT de> <20141106200635 DOT GP28195 AT calimero DOT vinschen DOT de> <20141106204222 DOT GQ28195 AT calimero DOT vinschen DOT de> <545C68BA DOT 3050007 AT t-online DOT de> <20141107101659 DOT GU28195 AT calimero DOT vinschen DOT de> <545D30DA DOT 9040507 AT t-online DOT de> <20141110105151 DOT GB2782 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20141110105151.GB2782@calimero.vinschen.de>
X-IsSubscribed:	yes

Corinna Vinschen wrote:
> On Nov  7 21:51, Christian Franke wrote:
>> Corinna Vinschen wrote:
>>>>> In theory there should be only one option -l [machine], which prints the
>>>>> local accounts of the current machine unprefixed (standalone machine) or
>>>>> prefixed (domain machine), and always prefixed for a foreign machine.
>>>>> The -L option can just go away.
>>>> I disgree.
>>>>
>>>> Why not keep the old behavior of -l/-L for user names of current machine for
>>>> those uses cases which rely on it?
>>> You are always free to change the passwd/group files manually:
>>>
>>>    $ mkpasswd -l | sed -e 's/^[^:]*+//' > /etc/passwd
>> Of course, and it is good that this is still possible. But this would
>> require that all existing scripts relying on old behavior need to be
>> changed.
>>
>> I still don't understand why this backward compatibility break of "mkpasswd
>> -l" was mandatory.
>>
>> Most *-config scripts using "mkpasswd -l -u USER" may need to be changed.
> Definitely.  The change is inevitable since most scripts using mkpasswd
> or mkgroup do so to create entries in /etc/passwd and /etc/group.  But
> this doesn't make sense anymore, or if so, only marginally so.

OK.

What will be the behavior of the predecessor of e.g. the csih function 
csih_create_unprivileged_user if called with USER without HOST prefix, 
machine is inside of domain and the user does not exist:
- create local windows USER and require the config script to retrieve 
the actual Cygwin HOST+USER name,
- fail and tell the calling config script to retry with HOST+USER 
instead (if possible),
- create local windows USER and create a /etc/passwd entry to support a 
non-prefixed Cygwin USER in this case,
- one of the above, selected by a new option.
- ...
?


>> Local scripts from Cygwin users which use "mkpasswd -l" may need to be
>> changed.
> They are not supposed to use mkpasswd anymore since they don't need it,
> only in very special circumstances.

Wouldn't it be better to let mkpasswd -l simply fail with an explanatory 
error message instead of producing non-backward compatible results? Or 
at least print a warning to stderr?


>    And then I expect that they will
> have to change the created files manually anyway.

It depends. One of my use cases relies on non-prefixed local user names 
which match the (also non-prefixed :-) windows local user names. The 
usual duplicates with domain users (Administrator, Guest) never resulted 
in any problems.

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 -