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=sP+rYc9sAx4TUMvxhZpv9Bn7bYUEdwL2ulEpX4LmRG6FHwtbhlube
	V6/9IvCWiYbx0ri3MJJ7W12ulqqdxtJj+KHqKWGrHtBsv6yRj9tagPwXO16HPzFO
	8CTiVsSYrvgsmLh0Ser7AEem2q5srEZsWZqnvIotnqO6rO89sdJMl8=
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=Qd9gmzIKp9mA2K2oulTXjb2XggQ=; b=jrrA3lT0HPtRd0pB17EMF3cnbmNA
	nLex6j2egdBfRS9Pws/SsZp7NHaV2XJab16EF51dKy/p3ibi/NQLIh1BkPQZn6nr
	t5vR+GydYwj2xddkpSQ8EvMROOQ+u3eaGnUttdIDSikjCKGxD0DQAXQIrNvo0JOa
	pwscmtlDrDzMmVw=
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=-6.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Sun, 16 Feb 2014 15:48:35 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Testers needed:  New passwd/group handling in Cygwin
Message-ID: <20140216144835.GS2246@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20140213143849 DOT GH2246 AT calimero DOT vinschen DOT de> <52FD63BC DOT 60800 AT etr-usa DOT com> <20140214104243 DOT GY2246 AT calimero DOT vinschen DOT de> <52FE786F DOT 9040203 AT etr-usa DOT com> <20140215125043 DOT GK2246 AT calimero DOT vinschen DOT de> <7F9D4826-E8D5-41E7-A8B6-B41922FE6E1C AT etr-usa DOT com> <20140216115612 DOT GO2246 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="DCmRZ841GpRfzaEr"
Content-Disposition: inline
In-Reply-To: <20140216115612.GO2246@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Feb 16 12:56, Corinna Vinschen wrote:
> On Feb 16 03:30, Warren Young wrote:
> > On Feb 15, 2014, at 5:50 AM, Corinna Vinschen wrote:
> > > No, that's not right.  We have two mechanisms implemented you can
> > > choose three out of four possible combinations:
> > >=20
> > > files only
> > > db only
> > > files, then db
> >=20
> > Yes, I realize that.
> >=20
> > While composing the previous email, I considered a 2-Boolean design:
> >=20
> >    ignore_db=3Dfalse
> >    ignore_files=3Dfalse
> >=20
> > I rejected that design when I realized that ignore_files is redundant w=
ith respect to /etc/foo file existence.  If the files are present, use them=
.  If not, you have a DB-only configuration.
>=20
> What if an admin wants to avoid that files are read at all, even if a
> user manages to generate them?

Anyway, I'm willing to switch from /etc/nsswitch.conf to something else.

Let's assume we go with /etc/cygwin.conf instead.

This wouldn't set a bad precedent in terms of syntax and keyword
differences to configuration files existing on Linux, and it would allow
to define more settings which have nothing to do with passwd/group stuff
in the long run.

So, how should this look like?  Let's do some free floating,=20

  # /etc/cygwin.conf
  pwdgrp=3D"files db"

  db_separator=3D"+"
  db_cache=3D"yes"
  db_prefix=3D"auto"

And now the new one.  I have getpwent/getgrent practically ready to go.
It's just missing the setting to restrict the enumeration.  It occured
to me that an admin or a user might want to restrict the enumeration to
a specific set of domains.  What about something like this?

  db_enum=3D"local primary trusted_dom1 trusted_dom2"

"local" and "primary" being fixed keywords for the local machine
accounts and the accounts from the primary domain.  Everything else is
treated as a domain name of a trusted domain, and the name can be given
as flat domain name as well as as dns domain name.

Does that make sense?


Corinna

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

--DCmRZ841GpRfzaEr
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJTAM/DAAoJEPU2Bp2uRE+gieUP/39ltul1SdtAWWnkm5aT0Coo
4POPvFISOpi9DLZRYgLnrQc4Ze0UD5TtBkLSE6FGw6aIvzixbavy8kRjKP6u8rVo
Fjd7wJxAUHx2nyVmq4RuTYoGqg4dbMMUF9dQVrmtrjiqjI+FEtBD9i8MTTcUrJB5
aoo/1YlstL8HgC/W/vVFyK6G/kk7SLrT+94cmDTeo839n5XQx7f3OUjMmaNikzYA
kaaRj7FRIsro3fzKuSt3gWG/SOIpoKIxIoz9iLuIXmWev29VIYioV32VM7VXsKT2
OvP2/3mtazt4vYIJ6FtbqUiJ/kCyZohgJYVAwoqFOFz50ZO2M0Qh7cG7zbsyedPW
x09rTp4HN8mWWScsFH6focmY7ehcatqG6QP8zl1vxUMKiH3/d7+E+oxPpFm4YCFX
IIfnfAsJ3OUE79SdL08Nhy2yADd6JDXES7ikdntwf/WRgHNWj+psh2keBq+pSJOx
RJyDOq1wqrKCyjkjrZIH3Gwiz24K42pOkmhRzGsSmy0kh0FBZYYHIh6vkxQIvhGV
DRW7E4R6qXqNE+48L3tFfZpn+StSnPzM+Qec0IWYLHkJavcyYAmS6CTMF4EX12wc
L7LXPDDC71IIeBMsRdP3/sfg3son7/nCFMamO9I2Dghkr3m6Zx6mGyHgZJffPnTI
oL7deMhLM/i6YbJhvO35
=wqKG
-----END PGP SIGNATURE-----

--DCmRZ841GpRfzaEr--