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=YVSrU+ZfgN9rvs15G/dW+LIKrUmPe9BMZ/EYZGdDszGIyVFGHB0wy
	ypwQYGNvjMDkspC1A0EATxHB85719AIOvUUKXX2nKpdsFeT0kevLHcPeh0j4xVnx
	3072T8t1Zam9yOv4yZ4XWKCQZc1G1jpYDSWs2z6QTHGvQ82Pl7ZOsY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 30 Jul 2014 20:40:09 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Simplify AD integration?
Message-ID: <20140730184009.GS25860@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20140730134716 DOT GM25860 AT calimero DOT vinschen DOT de> <lrbcnp$bg5$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="TXIPBuAs4GDcsx9K"
Content-Disposition: inline
In-Reply-To: <lrbcnp$bg5$1@ger.gmane.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Jul 30 11:15, Andrew DeFaria wrote:
> On 7/30/2014 6:47 AM, Corinna Vinschen wrote:
>=20
> I have not been actively watching this thread but if I'm correct we're
> adding NIS like capabilities to Cygwin so that /etc/passwd can easily be
> filled with say everybody in the domain? If so then bravo!
>=20
> I also take it that it's not ready yet either.

It's ready for a given value of ready.  I'm just looking for certain
details which needs to be clarified before the stuff can be released.

> When it is, how would I
> install it?

The existing code is in almost all developer snapshots of the last few
months.  Just try the last one from http://cygwin.com/snapshots/ and
read my preliminary documentation attached to this mail again (and
which, incidentally, is now in the offical docs in the repo as well).


> >So I'd like to ask a few questions to which I'd like to have some brief
> >answers, kind of like a poll, to get a better idea how we should
> >proceed:
> >
> >1. Shall we remove the leading '+' from the builtin account names
> >    or shall we keep it?
> >
> >2. Shall we stick to '+' as the separator char or choose another one?
> >    If so, which one?
>=20
> How about "@"?

Dunno.  It *might* be a good alternative to '+'.  Personally I just
dislike that a '@' is a less "light" character and it might give a wrong
idea.  Email:  name AT domain.  Cygwin account:  domain AT name.

> >3. Shall we keep the `db_prefix' variability or choose one of
> >    the prefixing methods and stick to it?  If so, which one, auto,
> >    primary, or always?
> >
> >Bonus question:
> >
> >4. Should Cygwin downcase all usernames when generating the Cygwin
> >    username, so, if your Windows username is 'Ralph', your Cygwin
> >    username will be 'ralph'?
>=20
> I say downshift them!


Corinna

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

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

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

iQIcBAEBAgAGBQJT2TwJAAoJEPU2Bp2uRE+g7pgP/AsSjtwTdAPkMbxJU3H/+Abq
Z+w/jSckGZsWaZ6ZUnCP64wy9bCeX8ECWs3lEOgDBFUl4GGZU7vAKkPlkVrQn4lC
02Y0K3DeeOlyaJEJosmNkU14PePJHqt/kHEW1BwiuHzFSaa9paUePma43fld/RWy
i+jVlsJfJGj1bJtKbUqHN9lnxyX1czmySKiFNujhNBrpOaq/zvXJTmYD1JMJ4lxx
/CeTBpaTVrckNlkPMSS6jRr9iQ1nom/9+aswoxrnD8elvM4S65SW9LYF/2WAjux6
9/G4qcZB45EoxMiX19/TVKuGPs4K9Kohe4LD2vnZPY1LnTHgxZLSarWDuv2Lg1b+
RYr31l0G4084CyorUEeiXQK/dPzWfgQ5vLGwQBgOIU+zBNfO4P/rX+1EhDjcIXrf
VcgE55Mcw4ay5Tb9O5aiEI30v+aukLTEZ/KvGC9Kx82eZvPsjKx/5AeErX2CAxip
1zqqtZwJXshIrkU4AhXrg3KlsfCE+hLJriwOSYDxZQUYuZw768HQA9+2ufUrpK9b
fhSJrLJAjMBA/tyUD985TqT0AVoyh0ra+Faq7j4UgYQZWnQsz+NfkKYDKZzXBpLC
KHho5ly2xBrHUXgW0oZh4wfPP207HGwlV3U7H6s9mrZwp/dC4mEASYVYzWV+BYkH
RgEcoad7uaFzPiHuO5Ur
=QdHn
-----END PGP SIGNATURE-----

--TXIPBuAs4GDcsx9K--