DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=DZWKNDLVL4uYnQvs
	PV/SMblI0bUV5PoEYG9JR8E7LnGbab4qwM2DIcC/v06i51eR/L8HcQBWkc4tlDQd
	/0OYG6u3LV87Ql7Pmj5sEvOqR04Onr3hFT539XXtwY92KpghHZic/3vNt7jj05v2
	GtOtXyN35BMO9JrABqUbnRvmHyc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 6 Nov 2014 23:03:35 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1249692221.20141106230335@yandex.ru>
To: Christian Franke <Christian.Franke@t-online.de>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
In-Reply-To: <545BD14A.8080803@t-online.de>
References: <announce.20141105164319.GA31314@calimero.vinschen.de>   <545B17B8.5010509@t-online.de> <20141106164915.GG28195@calimero.vinschen.de>  <545BBF4B.4020400@t-online.de> <20141106185019.GK28195@calimero.vinschen.de>  <545BD14A.8080803@t-online.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Christian Franke!

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

Did you actually tried running your scripts under new Cygwin DLL and see these
failures, or you're just theorizing here?

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

That's up to script. You can also fix it with a simple ${USER#${MACHINE}+}
macro.

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

If YOU need prefix-less local names, YOU create them.

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

Not supposed to work that way, I'd say.
The whole aim of the change is to get rid of these fails, not to help users
create them.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 06.11.2014, <22:59>

Sorry for my terrible english...


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