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=KTow9e6xhXvRqecigSGdWUMYNzHM4+qKv1j3QoCdlNF0Bem47BNZV
	R1xSRPzB11eKaA45XWd4dskeuRwt+7AxFcs5rWcJb6xy7chNewnQOyPWzc4Ug04U
	xBpBjBsocSfiHW9R042zcOkAxUHsMht+ORTIXhcaAUldSvdOOptj6g=
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: Fri, 1 Aug 2014 11:31:11 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Simplify AD integration?
Message-ID: <20140801093111.GB25860@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> <53DA441F DOT 2260CAE7 AT boland DOT nl> <53DA4FE0 DOT 4020307 AT redhat DOT com> <53DA6326 DOT 7C5690BB AT boland DOT nl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="6pjpgtPchv3bUQQn"
Content-Disposition: inline
In-Reply-To: <53DA6326.7C5690BB@boland.nl>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Jul 31 17:39, D. Boland wrote:
> Eric Blake wrote:
> >=20
> > On 07/31/2014 07:26 AM, D. Boland wrote:
> > > Corinna Vinschen wrote:
> > >> So I'd like to ask a few questions to which I'd like to have some br=
ief
> > >> 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?
> > >>
> > >> 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?
> > >
> > > I'm a legacy man. So I would say keep the MS symbol and use it like t=
his \daniel,
> > > \SYSTEM, etc.
> >=20
> > But you'd have to write that as '\daniel' or \\daniel in the shell, and
> > you also cripple tilde expansion.  That's why we already ruled out :, \,
> > and / as non-starters, as mentioned elsewhere in this thread.
>=20
> I am not only a man of legacy, but also a very opinionated one. So give m=
e some
> slack when I say: the whole thing is insane. This would mean that from no=
w on, I
> have to use constructs like ~+daniel ~+SYSTEM in a Linux shell?? Bizarre.

No, of course not.  Please have a look into my preliminary documentation.
and try the latest snapshot.  Add an /etc/nsswitch.conf file with the=20
following content:

---
passwd: db
group: db
---

Then restart your Cygwin shell window.  Call `id'.  It will give you a
first clue.  Then have a look into the documentation and play with the
nsswitch.conf settings described in the last section.

> On the other hand, for the sake of progress, but keeping legacy there wou=
ld be only
> one acceptable solution: use the tilde symbol. A user could then be refer=
red to as:
> ~daniel.

Since domain-less prefixing is only done for builtin accounts, it
won't affect your user account anyway.  But still, the tilde would
be bad.  If you want to cd to your home dir using the tilde
expression, you'd have to use it twice:

  $ cd ~~daniel

But, again, this won't happen anyway.  Your username is either
"daniel", or "DOMAIN~daniel" (assuming you use tilde as separator).


Corinna

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

--6pjpgtPchv3bUQQn
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJT215fAAoJEPU2Bp2uRE+gQe4P/iDHjM23f6obbEzDKIOrQ4D4
bOhxvwPT9hzlnmENe6yZrnrHis6jOnriI5zZK4gUFDMhBoygD7oDYivTA7nJopW2
yYuQywTD8usFufoawvC2rdWS8vpvscR/2FNbpobtfwbiShXxkMJfLMPAmOSaiS8u
OR7xEx+Z7i4ntKJgGs49YLeiRo4u87g8o+FKbBKpRjb+PfwgcJD4OQdHEpkB4SfV
jawG6E6CvNEcJwzVa1yhuzlDiwVc6uMSEAEcWmG+ZFZ8eAljE1rnQoedCBEau2xJ
uGA0zZwxND0ZRpxB651UlEXVBbJdy4tiwgXnIhSrp4K+ha8Vj2kc0kvKWzuB6/73
o+KTTMKWV/3Ese1R2c6Z2Iw0MClUC9FgXtfjJBZndj40gH2hPrTNA8N5VMN3CMo2
4AISzDIJAGQxb2K9E+n2jtwJMDtIxI1Kk2JYGRfGZ0LHH7NisD1mTtJQDvJPBiNa
SNLwQFzQwA5C20aaszSWpk9mV7/KHjLEenT7uN6iN0ZE9wuhnjBpKhLtYHtDFkzC
FfDXQMsfkX4AwRIAEi8YK+q2Psoz8NGocgoMy8+tBdzSWTUnK80t34Ldv3x31hTl
K3bX5H5kS/zqsChdev2oN5UFAQ1qy1CVs7j/FKjcwobYTgtClFGzSBeAux12FTNN
Z9c1CHkChS2DjVMDNXTG
=igWl
-----END PGP SIGNATURE-----

--6pjpgtPchv3bUQQn--