X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.0 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_RW,TW_WX,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4C7FB49B.70808@bopp.net>
References: <AANLkTima5VbUF2XFvv00ptE1L=9c9BT2hOOM8td4hhUN AT mail DOT gmail DOT com> <AANLkTinZs2FvqFtYueGR0-Wg5L9veTLaE7+SJa56R-r4 AT mail DOT gmail DOT com> <i5li5e$tse$1 AT dough DOT gmane DOT org> <AANLkTi=Z8dSKa6fWt6m2dKMG8gVnG4LEZuq+QN1Y=Qb6 AT mail DOT gmail DOT com> <AANLkTinHHFQSrqJuzhnLzUKLw321Pe2qc=2mkao2Z5iU AT mail DOT gmail DOT com> <AANLkTimzCUXnhekxmjDmmgHgw+ocKt-xBh5Ei=HF5QsB AT mail DOT gmail DOT com> <AANLkTikLOv2xn2RodtrRfgdGnSYYZrMeKyWBfDA67Js1 AT mail DOT gmail DOT com> <AANLkTimBGg8vpw9bFcbzvaieTv5DvOSbK5ytJnpLcVP0 AT mail DOT gmail DOT com> <AANLkTimFJS7THKkUa76rBMWkQWYpe5r=p3prETQgqymv AT mail DOT gmail DOT com> <AANLkTi=zev2TeGMvk1fxkx8e8xVRW9J2V5JP7C3S72Bt AT mail DOT gmail DOT com> <4C7FB49B DOT 70808 AT bopp DOT net>
From: Vasya Pupkin <cygwin AT bsrealm DOT net>
Date: Thu, 2 Sep 2010 19:05:22 +0400
Message-ID: <AANLkTinNguivfYkt0ZZ0uQSFxHxx0JfyR0w3nx7Zv1yJ@mail.gmail.com>
Subject: Re: Fwd: Windows File permissions are not being inherited - Cygwin 1.7 - Windows 7
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

If you read again very carefully, you will see that I modified
permissions AFTER I noticed they were messed up. Ok?

In my case, these additional permissions were allowing everyone to
modify files. Not harmful at all, indeed. I do not remember all the
details, I remember these permissions were everywhere. So I just
replaced everything with proper permissions and disabled acl support
in cygwin. The only problem was setup.exe but now I compiled it with a
modification and this last problem gone.

I understand that I do not have all the details required for a bug
report. And it wasn't an attempt to report a bug. I was asked why I
care about permissions, so I answered. Anyway, the problem is solved
now, I also submitted an easy patch to setup.exe source for everyone
who want to get rid of this problem as well.

If I ever get into a problem with permissions again, I will try to
make a proper bug report instead of just fixing permissions.

On Thu, Sep 2, 2010 at 6:28 PM, Jeremy Bopp <jeremy AT bopp DOT net> wrote:
> On 9/2/2010 12:49 AM, Vasya Pupkin wrote:
>> No, it wasn't a mess of my own making. I did not ever touch
>> permissions, and it was a clean install. I don't know where these
>> permissions came from, but ls -l displayed something like that for
>> most files:
>
> I read Andy's comment to mean that the mess of your own making is the
> result of you changing the permissions, not the existing permissions as
> left by setup.exe. =C2=A0You made the mess (or correction as you see it) =
and
> are now fighting with setup.exe to maintain it.
>
>> drwxr-xr-x+ 1 user group =C2=A0 =C2=A0 =C2=A00 2010-09-02 09:32 tests
>>
>> This "+" sign after permissions string indicated non-cygwin
>> permissions which was impossible to remove using cygwin's chmod. And
>> since permissions are not inherited, it was not possible to mass
>> remove them using windows either. So, I just removed all permissions
>> and forced their inheritance. That solved all problems, until I
>> updated installation using setup.exe.
>
> The "+" indicates that there are further permissions specified as ACLs
> for which the getfacl and setfacl commands should be used to view and
> manipulate, respectively. =C2=A0You would see the same behavior from ls o=
n a
> Linux system which had ACL support and extra ACLs applied to a similar
> file or directory. =C2=A0There, too, chmod would not be able to modify th=
ose
> ACLs.
>
> What your example does not indicate is that anything unintentional
> happened with the application of permissions on that example directory.
> =C2=A0Nor does it indicate that the given permissions are in any way harm=
ful
> to the maintenance of your system or the use of the files and
> directories in question.
>
> Where was that directory located? =C2=A0Did you create it, or did setup.e=
xe
> create it? =C2=A0What problems do those permissions cause?
>
>> Believe me or not, but I really did not touch any permissions until I
>> noticed that strange behaviour. And I am the only administrator.
>> Machine is not a part of any domains. So, unless it's a kind of black
>> magic, there was (and maybe still is) some issue with permissions in
>> cygwin. That is why I don't want to use them.
>
> I'm sure the Cygwin developers would be more than willing to patch any
> defect surrounding the incorrect application of permissions to files
> which is the result of Cygwin itself or setup.exe. =C2=A0Unfortunately, y=
ou
> have not demonstrated any such erroneous behavior yet. =C2=A0It seems more
> likely that you have a small misunderstanding about how the permissions
> you see work and how they are represented under Cygwin. =C2=A0Have you re=
ad
> the section of the user guide which discusses permissions under Cygwin?
>
> Perhaps, you have found a genuine defect. =C2=A0If so, you need to provide
> more data so that someone else can reproduce the problem. =C2=A0You could
> start by installing another instance of Cygwin into a fresh directory
> (this won't affect your primary installation) and then demonstrate the
> specific files that have faulty permissions and explain how those
> permissions will lead to further problems.
>
> With luck, someone will be able to explain why things are the way you
> see them such that you are comfortable accepting how Cygwin does things. =
:-)
>
> -Jeremy
>
> --
> Problem reports: =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/problems.html
> FAQ: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http:=
//cygwin.com/faq/
> Documentation: =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/docs.html
> Unsubscribe info: =C2=A0 =C2=A0 =C2=A0http://cygwin.com/ml/#unsubscribe-s=
imple
>
>

--
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