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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=sMBKqeezI1oLmF8EDc/PTqqtRk8uCHGDyMQ447jgzxEWr+5PgDIs5
	PMPrBJw5PP1TsTZGJYXBQVCgi3odVGgjXMkPsFhG/V+nl4YPVA2DBPJFRka5Cwhp
	wA23oYSqhfSsRBLGwK823rnNhgKbFUJMDFYJwu4j3WAh7Lgkpzzt6A=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=+ZL0U/maiaaLCB5VL1GKny583gQ=; b=gpS8h1mJp4tKWMNtyhZaBvkvTZJU
	lerbT7csmlikih74qHa8RO/6/GwMPJjNuvXfDEYFudpYxssD4Okf3DjULNDexVBH
	bJ/RiKp6GWQLWwyLk+bm8n2gkT2YajT1l8C0GyVIom6QEAfk9dmC6aiqVR/N6paG
	V934koaPuNKhL6M=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Thu, 6 Nov 2014 21:06:35 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
Message-ID: <20141106200635.GP28195@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <545BD14A DOT 8080803 AT t-online DOT de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="7vAdt9JsdkkzRPKN"
Content-Disposition: inline
In-Reply-To: <545BD14A.8080803@t-online.de>
User-Agent: Mutt/1.5.23 (2014-03-12)

--7vAdt9JsdkkzRPKN
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Nov  6 20:51, Christian Franke wrote:
> Corinna Vinschen wrote:
> >On Nov  6 19:34, Christian Franke wrote:
> >>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...
>=20
> I would only fix it back to the old behaviour (mkpasswd -l =3D no prefix),
> sorry :-)
>=20
> 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).
>=20
> 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...
>=20
> 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 then... why not keep mkpasswd -L and use that instead?

> >>But PLEASE keep the ability to create local users/groups without a pref=
ix.
> >>Otherwise useful configuration defaults (mail_owner=3Dpostfix, ...) wou=
ld be
> >>no longer useful because config files must be tweaked for each host
> >>(mail_owner=3DHOST+postfix, ...) for the sole purpose of[1]. Some of su=
ch
> >>technical users (sshd?) might also be hard coded or a config parser mig=
ht
> >>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.
>=20
> 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.

PTC?  As I wrote, I hope I have something ready next week, but the
csih heler script is pretty complicated.  I never expected having to
maintain it :(


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--7vAdt9JsdkkzRPKN
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUW9TLAAoJEPU2Bp2uRE+gtRUQAIQYenr1hIQRzc5YgVdAyOgz
LsXldl1z1x8EbMstCHwaU65DB8I/34vDlDIAdOvB5iDinRlSRlZxvJjxN0Qj3Ztk
tczpWGLVf2r6jeog7Uq7ulQF7P+3YZ+x/+KUAD4GnXB3dnQeUmDwCss9Ft6Myh4E
+/F4GygSMvQ8W3tCD64ERZ2gssNRYJQifQuW2WfG8x1tRXp/DauK5tpuReBoW5DZ
JTi0ILeRYTOFXz3MtMvxyaV64SqqZ/phKxiaxNnfYYw9nepV3ymdwwJTdPSbqknC
9EGk3OnkVC4iP5yRFpFYFmfQ+N7XeImLoDSz6Mf+S/vDvWCkEVArU9F2+oj24DOH
T/x1xygbNshbA4uGiNk+JImBTycVSSrf2sy75pJc7GUyFkOnGz9FiKtyGshkCYPX
sYq1XwIuboWKorid0o42XbOjeygpsjtIN2d3WwKUEKHLeMUsSZrwOh1EVau2qgSd
EeinDTEdUuL85fSPKeQX1EbpY299ggiLZm0+WnRd5FqPZdWDLTML6qO6A6ia/daY
BqCOIWqjUeDDT5IhdVqUmvgR27ZTab0Ymc/ZyFeYEc1CsTmsaODOOPmViS5r7zMO
3MhkOthJYKOLAGhxhyseQ/98QCuGNsVdgeppr3dl5i3GIRCCmQM4r2n2U+21wjRc
Qb/3A/zDqMXsC6XbVZQi
=Ri+n
-----END PGP SIGNATURE-----

--7vAdt9JsdkkzRPKN--