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=DAPGhquwV3AACjcc8lQhRHFmWz3UqX4fFVuEBjaKW9rCBieosucdV
	3VwUCLbMRX57JV9W4/+7pPBlj1nrPDoNVjOcdJozEWj5SoaTibUpazZbEZAI1RSY
	Y3PDebehnOO9PS/1sDUbCU8n14Z6zFgoUvU/Uan0JYwUQO8X5Bo4/o=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 10 Apr 2014 21:04:24 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
Message-ID: <20140410190424.GK2437@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20140410145323.GB2437@calimero.vinschen.de> <5346B667.3040704@breisch.org> <20140410152809.GD2437@calimero.vinschen.de> <5346E55D.6020405@etr-usa.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="SVeEiVwWO9F1slJ8"
Content-Disposition: inline
In-Reply-To: <5346E55D.6020405@etr-usa.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Apr 10 12:39, Warren Young wrote:
> On 4/10/2014 09:28, Corinna Vinschen wrote:
> >
> >The only reason I dislike backslash a bit is, that the backslash is
> >the escape char in the shell, so you would have remember every time
> >you type in such an account name to escape the account name,
> >DOMAIN\\username or "DOMAIN\username"
>=20
> Is this DOMAIN\username syntax merely mimicking a Windowsism, or
> does it directly translate into a semantically meaningful construct
> to Windows?  I mean, do you have to parse it and reassemble the data
> for Windows' benefit, or do you pass this string straight to some
> Windows API?

Right now, since the separator char is configurable, it's of course
mimicking and converting to the windows style where required.

> If cygwin1.dll must premasticate the string for Windows' benefit,
> you can use any separator character you like.  In that case, I'd
> think forward slash makes more sense, since it says, "This works
> like POSIX paths: cygwin1.dll is translating this to something else
> for you behind the scenes."  Backslash signals that what you're
> doing is something Windows understands natively.
>=20
> As for your original question, I can't see why you'd need it to be
> configurable as long as it's escapable.  If you can escape the
> delimiter, then you can hardcode it to anything you like, since
> there's a path out of any conflict.

A local cygwin user told me that the users in their company would
probably be confused by the '+ or, FWIW, any other non-backslash char,
because they were drilled to see and use usernames always in domain\name
form, or even in domain\\user form when logging in to Linux.

I like slashes a lot more for obvious reasons.  But maybe, and that
wouldn't be too hard to implement, we could accept account names with
slash and with backslash, just as we do with pathnames.  Output of
usernames would be with slashes, of course.

Well, just an idea.


Corinna

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

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

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

iQIcBAEBAgAGBQJTRus4AAoJEPU2Bp2uRE+g8yAQAJTVQEDHOy9LivQ5FKBERYEA
5dh9x7okyjwnqeI2QKXCBBTSHUECsdBzTarvS+u3Q74Hj70VNXqQn4gvdApcRQoG
Ikk86W8w/cyWDtUTBrGS5ilczl0cyh6vhfBokxV8Bo2FbJ0HwpdUB0fBjUbwSLqb
WfaSAxCARa2WX5wK7E6DrZItJu9/wohU0KX5xudWd1lDv5dwHTebgf2hL1QXaP5m
y+Tv4oA0cvsaCfpopVjrWhdsMRznfCUVjdFbniQk6rTcCNNGUFvxzBzsuRLySq4W
n8oECRO5eXIyn61CqLSl5wAHskXpfppBIn0hJYtx5ntbistidQjI5H1/u3foWGtD
4aOeymTjEKRt4+xi6iFt6yCKygjyQiJ78SBY3Wco88vkkFQvnIC+p1MYfI2hVrvZ
u/6fz9RPAni6vZqmXTK16JDh6SDNiN+Qq0iHyXTzXocOXFYWnD7OvhFCX/VFHcmr
+o4oi240WeXWd1ZhqlDSKkB3OmWRwI9uVF8xYu26Nam+ywmiKd7xP4E4xn+g0xK8
pz9PF3Wxdav0gWFMrY0/+vrOFjiH+2tsJ+jKrZ1110ActLExfq0eAsGiBq1eHEVX
17QMrBiyu3unmOfGjFtTC5budiKEs7UJp3cK450OToYsWEFEu5j48GxkKbNbinSp
Zb4ngCz5+LCeLytyfl7d
=p8V9
-----END PGP SIGNATURE-----

--SVeEiVwWO9F1slJ8--