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=L7gK5/EuoneVSmsUDU0F3zEqdnvNtEtYNxxNt9Lww2EZ7dnANvrCo
	ofrZ80v8pcyPNLkvZdyCE1H+owBhK4nGrY+9+oMHvH2kosS8FXh5opG71KZz0AHs
	JcBTmwcZ9KaWla9xzaCKRhXXttP4Lp8wrJ9OAYsSEuP+bYpTVgrOpg=
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=BUNph5xdQH/ps5aWs+PSYrhXlso=; b=ogLDNV3OYpTFHEhP+1LylYYOvWqA
	Mb8vDcS+37W9FpHvNUlWuie1LZK4MSC4a3wBfPxVV1ltx8+2qJj7g4Ke5x5QtPfM
	fwyljNrWUFvBqlKNG9URzk+hByz6jylWkfjN+DEVP8VG9FtsW/OjH5g15Uw/rlMy
	p4NJUb/+oKV6OJw=
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-Spam-SWARE-Status:	No, score=-100.9 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=Administrator, password, states
X-HELO:	mout.kundenserver.de
Date:	Fri, 15 Feb 2019 22:31:59 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Windows to Cygwin username mapping: Domain before local account when duplicate name?
Message-ID:	<20190215213159.GQ2702@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CANV9t=SNfgP-CA32yfPwLv2=d0F8xtpdCT4o_wwGFGE+F3SEuA AT mail DOT gmail DOT com> <50cba8d1-4794-8db9-d1f3-ab9476421db7 AT gmx DOT com> <CANV9t=QQ1higAt1qeDF4fckkz_6eqQJtdhau8+uhrAvGtWUK_A AT mail DOT gmail DOT com> <20190215163817 DOT GI2702 AT calimero DOT vinschen DOT de> <CANV9t=Rm+su=qDqdFN-LqiMLEAHJD7WxW_OSqqSpqgeb6ir++w AT mail DOT gmail DOT com> <20190215202936 DOT GL2702 AT calimero DOT vinschen DOT de> <CANV9t=SdQPZw_VF95HwDrVRU1KzdHA61GJBRgA1weHryHUO6-w AT mail DOT gmail DOT com> <20190215204326 DOT GO2702 AT calimero DOT vinschen DOT de> <CANV9t=Q5M+V9TPEN-GaGzLtK_8AO5fUenajQ+T-VZX6+kbrMMw AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CANV9t=Q5M+V9TPEN-GaGzLtK_8AO5fUenajQ+T-VZX6+kbrMMw@mail.gmail.com>
User-Agent:	Mutt/1.10.1 (2018-07-13)

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

On Feb 15 13:59, Bill Stewart wrote:
> On Fri, Feb 15, 2019 at 1:43 PM Corinna Vinschen wrote:
> I think I see the problem. The list I posted (above the one you are
> apparently referring to) has the search in a different order.

I'm not only "apparently referring" to that list, I pasted it verbatim
in my reply to you :)

> The section that starts with "Let's discuss the SID<=3D>uid/gid mapping
> first. Here's how it works." states this order:

It doesn't state an order.  It describes the mapping from SID to
uid/gid, and there's *no* order at all to it, just a description how
certain SIDs are mapped to certain uid/gid values given numerical
recipies.

> I was assuming the first section is an orderly sequence of searching,
> since that's usually how Windows works.

Windows usually maps SIDs to uid/gid values?

> The second section with the examples seems to be a different order,
> and would seems to be the order Cygwin actually uses.

Both sections have examples.

> I was just wondering if that's by design or by accident, since it's
> different from the typical order.

What is a "typical" order?!?

If you login locally to a domain member machine the default domain is
the logon domain of this machine.  If that's not what you want you have
to choose the logon domain of your account explicitely, even if it's the
local machine SAM.  Windows will not try to find the user name locally
if you didn't chose it explicitely.  You get "The user name or password
is incorrect. Try again" instead.

The only exception I'm aware of is the "Administrator" account, at least
in Windows 10.


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--oiL9LJXJsdjS5rzq
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxnL88ACgkQ9TYGna5E
T6Bp6A//Yx8sIeo9lEmGt7duW3wKwPpOdcxp0JaDNeiZfZNAg0922G70rwa7gcxh
EJgyoKlWYnBo2h+yorAnuodwGi+i2NBzyxJOEmMtWPBnlG2Lg2LWbSuxWJW0BjfA
Kkpwe2AgcstaJ1r7JArYCI+ckKV9nhwS7wqcJX7WaKpIsXh1wGSW8kjnlpFC1fWd
aT3yMXft1HjziVdBgVlzbZ3ZgoXbmTR1SbllEatCr41iFG0iYAk2H798pzt0FbZt
jHJ7li1MVArx3fUlVhlZMHDeAWVVr94UCBmSb56R6janaVfuqVaLDR3p/E6Q04gz
u0an4s0MDw7WJqrfvOVLsTOHAEUw5xg+oVyPyHmlYXHBELVuAYgKSFMvmP/ntxcO
yxUO9DhvjFOtkpB+bwhopXdzrkAUbfZvGNKAp5flBkwnCGrdNjgM2OjZLH4DYiJm
j4hUDiqTVVDu9FF43mWrY4UcMZARBDv6wOyqH8jTY7QuTwXSrXScpd+okIlArlA9
nvFThpT720F4hhGW3pR9b+HkB3PjR43UrLyGzLFjhT4yXINf7HopJS3L3eOIysVG
CjFleIpoO2q/UCyvH83IaucQoW8vkjlW5b7vlXjcrfmGjDt+AUw1V9owbdFvCTI0
Cr2I6cBCHurAGMlNpE4YaBVzpFQGhaMvPOi6R+Flu001kOjFLBI=
=is+0
-----END PGP SIGNATURE-----

--oiL9LJXJsdjS5rzq--

- Raw text -