X-Recipient: archive-cygwin@delorie.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=WD1J2FNM2WrwkRZRhZR7FPEghnS0xNf1Ou0rqMnX0D2z3ueKDrddb
	gGvFZGZe9AW2/Xfhu/j67JNzy9rxbuICRELcrRNz/S9Nau1tbsOpnBbiY/4Ul7fH
	EWD8+Zc5zq4Q8sY/XjLpyRWXuzrkssucI9XzCq61jtAdAcoiiSIbOc=
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=ATH4cWwnUzZ4yex5vZ0Gm8l8e8A=; b=fzSP+RKajhqrD5h4Bz68c7mwMeVj
	DaYUfUuEnn/ikIq0URxhRtS9pQ+ST6Nj2LvkOkTpeUtmf3OhssVE1FUiV+TuIXSw
	a8iXYCYJv3rCHg/uJILaKGKoQEOdeaORir/TAbd8muE2cQqnP8UNUZizl+bf+qli
	HecgjB7vpyDrs00=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-101.6 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=credentials, rights
X-HELO: mout.kundenserver.de
Date: Thu, 14 Jun 2018 13:31:32 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [bug: csih] Setting privileged rights to cyg_server fails on Windows 7.
Message-ID: <20180614113132.GB2587@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20180613224901.d2cf679cef8eab89a834c494@nifty.ne.jp> <20180613181407.GT7851@calimero.vinschen.de> <20180614062218.eee6704d2ebc62383a2927c7@nifty.ne.jp> <20180614091642.GA2587@calimero.vinschen.de> <20180614192957.2128dbee897097bddb0844e4@nifty.ne.jp>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="yNb1oOkm5a9FJOVX"
Content-Disposition: inline
In-Reply-To: <20180614192957.2128dbee897097bddb0844e4@nifty.ne.jp>
User-Agent: Mutt/1.9.2 (2017-12-15)

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

On Jun 14 19:29, Takashi Yano wrote:
> Hi Corinna,
>=20
> On Thu, 14 Jun 2018 11:16:42 +0200
> Corinna Vinschen wrote:
> > Thank you, too.  I pushed the patch and will release a new csih package
> > soon.
>=20
> I read the discussion in the past pointed by Shaddy.
>=20
> On Thu, 14 Jun 2018 11:29:40 +1000
> Shaddy Baddah wrote:
> > https://cygwin.com/ml/cygwin/2017-01/msg00233.html
> > https://cygwin.com/ml/cygwin/2017-01/msg00283.html
>=20
> My understanding is that if "Run as administrator" is used,
> LOGONSERVER is not set even if the machine is on a domain.
>=20
> Therefore it is hard to judge if the machine is on a domain
> or not when LOGONSERVER is not set.

Actually, I just tested this on a domain member machine.

1) I'm logged in with an administrative domain account.  If I open
   a shell with "run as administrator", LOGONSERVER is set correctly.

2) I'm logged in with a non-admin domain account.  If I open a
   shell with "run as administrator", enter credentials for the
   above domain admin account, LOGONSERVER is set correctly.

3) I'm logged in with a non-admin domain account.  If I open a
   shell with "run as administrator", enter credentials for the
   domain's "Administrator" account, LOGONSERVER is *not* set.

4) I'm logged in with a non-admin domain account.  If I open a
   shell with "run as administrator", enter credentials for the
   local machine's "Administrator" account, LOGONSERVER is *not*
   set.

I think this is a bug, but looks like we have to live with that.
Alternatively we could check for $USERDOMAIN, perhaps.  This seems
to be set correctly in all scenarios.


Corinna

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

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlsiUhQACgkQ9TYGna5E
T6AgVw/9EHpAFyNHidTc+IY5UWfbK90wJZXDvFAKW7cDlQh7Y7A5InYLFi6ybdwt
4uebgabuh+cnLAbW01SFO3QA77+M2k65criTi9U4ilM2Co3nePgka/wq3EGHWZSn
Pg9UEbxyGHLBVNUqwbeQGaH6UX0n92vb7niH416HHRuWITTSZzxmRJVkp7UuKcaK
rLvYZSDW3W9RJ4D/PG2ebIyPIh6t0S7dPrYIdy+lqlUcAP6nOz1JHDM4pyUlgAhQ
it4UbJHAxGt4vgvaVwFM+ko2AC3NnUYd1RBum8I9Ir/07NBe5BDNlCdxNsLvIrLS
31gatLgqTIYcVwsvg7Bgu1h0/f5btv1noiJh1GqoEcksuEDDsL3PcReMKDT7FUXA
SotHBOAsuhK0eHILimLo5cZbAJgswu/bMEY4qGhIviFyL371xgNySkCYQ7OdJdVR
tRdaZHwfUzjMGZB5SA3lflcRsWLzKHhxc4bwsyM2rLRWTdfuJe2A89KqhpRKEOXE
Ewm5WgiMYh2WpcYer6+ghS6jxuHq7mjm3PUf3COmgmpbSGD4stAxNEVd5CKq3CA3
4BaMkokKPXf4X1MP+t6HPdAfKm78Ibmqsf2d2+6aDR07FB+JT1PpM/f8X5fuvfji
oFbwznky/3s28Fn+RTeqk3ndVKXl6VNosX6PQMwKKvGUc6bjQuY=
=hyWy
-----END PGP SIGNATURE-----

--yNb1oOkm5a9FJOVX--
