public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.4
Date: Sun, 29 Nov 2015 14:01:00 -0000	[thread overview]
Message-ID: <20151129125921.GA2755@calimero.vinschen.de> (raw)
In-Reply-To: <1352387525.20151129021637@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]

On Nov 29 02:16, Andrey Repin wrote:
> Greetings, Kacper Michajlow!
> 
> >> Please also attach the output of `id' and of `getfacl . test test/test'.
> 
> > getfacl attached. `id` output is already in cygcheck.log
> 
> > In getfacl output this line `default:group:1001 <unknown>:r-x` looks
> 
> Uh-oh.
> Do you, by any chance, have /etc/passwd file?
> Or a user comment changing relevant information?

I agree with Andrey here: Uh oh!

The mkdir trace contains a suspicious snippet which is the reason
the mkdir call doesn't manage to post-process the ACL:

  [...] pwdgrp::fetch_account_from_windows: LookupAccountSidW (S-1-5-32-1001), Win32 error 1332
  [...] /[...]/security.cc:337 status 0xC0000078 -> windows error 1337

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?).

You're aware that you don't need the /etc/passwd and /etc/group files
anymore, aren't you?  https://cygwin.com/cygwin-ug-net/ntsec.html

For testing I'd like you to do the following:

- Edit /etc/nsswitch,conf and change the "passwd:" and "group:" lines
  to omit checking the passwd and group files:

    passwd: db
    group: db

- Exit all Cygwin processes and restart a shell.

- Call `id' again and attach it to your reply.  The uids and gids of
  your account and primary group should be different now.

- Remove the test dir, call `mkdir -p test/test' and call icacls on test
  and test/test.

- Try chmod 755 test/test again.

- Also, would you mind to attach your /etc/passwd, /etc/group and
  /etc/nsswitch.conf files to your reply?


Thanks,
Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-29 12:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 16:40 Corinna Vinschen
2015-11-23 18:09 ` Kacper Michajlow
2015-11-24  4:19   ` Andrey Repin
2015-11-26 13:24   ` Corinna Vinschen
2015-11-27 19:15     ` Kacper Michajlow
2015-11-27 19:24       ` Kacper Michajlow
2015-11-28 15:55         ` Corinna Vinschen
2015-11-28 23:20           ` Kacper Michajlow
2015-11-29  2:47             ` Andrey Repin
2015-11-29 14:01               ` Corinna Vinschen [this message]
2015-11-29 16:37                 ` Kacper Michajlow
2015-11-29 18:23                   ` Corinna Vinschen
2015-11-29 20:29                     ` Corinna Vinschen
2015-11-30 10:02                       ` Kacper Michajlow
2015-11-30 16:02                         ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151129125921.GA2755@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).