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=Z0zvbwLH7vKcTNyheLYPPA7qv4bx10x0SCSDPzS7ReQUaZcddmoTY
	gqizlSL1EH/VLDPEUs4rFs/j00mX87gadxFSzK+eB0AZHKp88X3LZHotcVaNwUnv
	PGj4Y5mPgmNuYbfq77B7MqTV60iptATezhLH2kBT8CkStJcd6Y3JKM=
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: Mon, 30 May 2016 12:40:02 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Permissions Problems
Message-ID: <20160530104002.GD6659@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <e5d9c7bf-a55c-fdec-78f5-92c956be383d AT huarp DOT harvard DOT edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt"
Content-Disposition: inline
In-Reply-To: <e5d9c7bf-a55c-fdec-78f5-92c956be383d@huarp.harvard.edu>
User-Agent: Mutt/1.6.1 (2016-04-27)

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

On May 16 10:13, Norton Allen wrote:
> I have seen problems similar to those reported in "RE: Possible issue with
> newest version of git (v 2.8) under Cygwin", but I did not want to hijack
> that thread.
>=20
> For me, the problems have been elusive. Scripts that used to work would f=
ail
> as created directories had bad permissions, but I didn't have time to sort
> them out. In the last week, I finally had time to read through the
> documentation on the ntsec page and try some tests, and of course now I'm
> having trouble reproducing the problems. You'd think that was a good thin=
g,
> right?
>=20
> I had been using /etc/passwd from mkpasswd, and based on recommendations
> here, I modified nsswitch for passwd: db. This seemed to work fine, and I
> decided I was all set.
>=20
> Then Windows update rebooted over the weekend, and nothing worked, and
> returning to 'files' resolved the problem.
>=20
> The exacerbating factor here is that I have a laptop connected to my work
> domain, but we use cached windows credentials when we are not on the work
> LAN (like at home over the weekend). In this scenario, cygwin was apparen=
tly
> unable to determine my username, and hence was unable to locate my home
> directory. The username is apparently cached successfully if I reboot at
> work and then go offline, but not if I reboot offline.
>=20
> Does this mean I need to stay with 'passwd: files db' for the foreseeable
> future, or is it possible to find the username in this scenario?

It's not the username per se, it's the fact that the db-only setting
doesn't allow o create valid passwd/group entries for your user.

So, yes.  In your scenario you should ideally revert back to "files db"
and create minimal /etc/passwd and /etc/group files.

/etc/passwd may contain only your own user account.  /etc/group
only the domain groups you're member of.  Everything "special" or
"local" will be picked up just fine by Cygwin then.  If there are
also files on your machine owned by some other domain user, it might
be helpful to add that account to /etc/passwd, too.


HTH,
Corinna

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

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXTBiBAAoJEPU2Bp2uRE+gQQ0P/3e+496y0h13JxdVsSRZ+YqT
jbSHiRT9aY8yS6gO/+hdyQydIMbgWSsWrQF2A5ocYRqnwzO8Q559rDEQcts0lOMJ
IYqK/1KWB4cp2v4WAt8st2HFNjP8XVptKonhEfFthSmJwxhLxA75lvdJ0jAcCk1Z
UxSU5Lxkk2uCapMp/mA/f39hV0xFbHXQfpfz2h48n+SR4o8zNLkfUsFsNnkVnCiO
QpDf1lWUwJY2QNWjnAbFiRAuKTfOla7hRoBy9qz8rQsIijiIjwls2560wrDHHRHE
o7WJ5VkGdLtzSOlnGDqjeFApC0dPyZnTOqv+aoOJxL5VCUaL0yS4dVtLgPv56zpa
tYkFputUk6jpYfMbDhoHC0DOGtNG7OVZqah9ZiG2UjuD8bZfYTTgQQkhT++YKfWL
L8GMNj4nGSHFOuLPj3OtmNm3KWh//Fy2VKNy80KYmVeLh48qNwPwPZlbmPDQZk9c
dcirOMG+D7qIOSXNpfoBJjuRJHzj9Q26sW9OWtGjv2rXIye28nKZ4hkFLcCsJlNZ
jnKyWfbFAVH4UTz+yfXV2nWQlAR6bYLReKz/Xpa68R0vFsRu3ikQQIS5iClA9z5o
wW0kLP38rTDxWpgatvWLGPv7B+ynn4pCK6jYgAnAkOT2GZQ6gvxZGHjWNPFCMl2W
jq6p3AWmkQm1rZnKfSWJ
=c+TT
-----END PGP SIGNATURE-----

--yLVHuoLXiP9kZBkt--