From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111589 invoked by alias); 30 Nov 2015 00:43:06 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 111574 invoked by uid 89); 30 Nov 2015 00:43:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wm0-f53.google.com Received: from mail-wm0-f53.google.com (HELO mail-wm0-f53.google.com) (74.125.82.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 30 Nov 2015 00:43:04 +0000 Received: by wmww144 with SMTP id w144so117625773wmw.0 for ; Sun, 29 Nov 2015 16:43:01 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.8.35 with SMTP id o3mr16844953wja.153.1448844181394; Sun, 29 Nov 2015 16:43:01 -0800 (PST) Received: by 10.27.87.195 with HTTP; Sun, 29 Nov 2015 16:43:01 -0800 (PST) In-Reply-To: <20151129201458.GD2755@calimero.vinschen.de> References: <20151126131633.GL2755@calimero.vinschen.de> <20151128155421.GX2755@calimero.vinschen.de> <1352387525.20151129021637@yandex.ru> <20151129125921.GA2755@calimero.vinschen.de> <20151129171043.GC2755@calimero.vinschen.de> <20151129201458.GD2755@calimero.vinschen.de> Date: Mon, 30 Nov 2015 10:02:00 -0000 Message-ID: Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.4 From: Kacper Michajlow To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00484.txt.bz2 2015-11-29 21:14 GMT+01:00 Corinna Vinschen : > On Nov 29 18:10, Corinna Vinschen wrote: >> On Nov 29 15:10, Kacper Michajlow wrote: >> > 2015-11-29 13:59 GMT+01:00 Corinna Vinschen : >> > > Status 0xC0000078 aka Win32 error 1337 means "invalid SID". And the >> > > SID 1-5-32-1001 is in fact invalid. The S-1-5-32 prefix denotes a builtin >> > > account, but the RID 1001 is invalid for a builtin group. 1001 is the >> > > RID of your user account, though, but that would be prefixed by the SID >> > > of your machine, which looks like S-1-5-21-XXXXXXXX-YYYYYYYY-ZZZZZZZZ. >> > > I don't see how this broken SID came into life, unless your /etc/passwd >> > > and/or /etc/group files are broken (hand edited perhaps?). >> > >> > I guess I only changed shell to zsh in /etc/passwd, but no other >> > changes were made. So I have no idea how they could get corrupted >> > either. >> >> They aren't. There is no 1-5-32-1001 SID in those files and both files >> look entirely insuspicious. Given that Cygwin doesn't create any such >> SID from scratch, I'm totally puzzled where this SID is coming from. >> Your mkdir trace output doesn't show this SID anywhere else either. >> This definitely requires more debugging... > > I think I found it. The problem was the handling of Microsoft Accounts > on machines still using passwd and group files. And the additional > group entry for the user with a gid different from the user's uid was > required to uncover this problem. This is fortunately a border case, > but the fix seemed to be simple so I applied it and added a comment > so as not to forget why we have to do that. > >> > Works. >> >> Ok, that's good to know. Now I just have to find out where this >> weird SID was created :-P > > That fall into place after I realized what was happening. The gid > 1001 didn't exist in /etc/group so Cygwin calls the function to > evaluate a SID from a computed UID/GID, and this in turn generated > the invalid 1-5-32-1001 SID. WHile writing this I realized that > I should harden this part of the code to accept only RIDs < 1000... > >> > I personally am fine with abandoning /etc/passwd and /etc/group. This >> > is good enough solution for me. Though there might be other people >> > with the same issue. >> >> This seems to be a bug in Cygwin, and with the content of your files I >> finally managed to reproduce the issue. I'm planning to debug this next >> week and, hopefully, come up with a patch. It would be nice if you >> could do another test then in your environment :} > > I just uploaded new developer snapshots to https://cygwin.com/snapshots/ > and a new test release 2.4.0-0.6 with the aforementioned patch. Please > give any of them a try. I can confirm that the issue is fixed in 2.4.0-0.6. Thanks for great support! -Kacper -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple