X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4C7FCFE2.3010407@bopp.net>
Date: Thu, 02 Sep 2010 11:25:06 -0500
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Fwd: Windows File permissions are not being inherited - Cygwin 1.7 - Windows 7
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> <AANLkTinNguivfYkt0ZZ0uQSFxHxx0JfyR0w3nx7Zv1yJ AT mail DOT gmail DOT com>
In-Reply-To: <AANLkTinNguivfYkt0ZZ0uQSFxHxx0JfyR0w3nx7Zv1yJ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

On 9/2/2010 10:05 AM, Vasya Pupkin wrote:
> If you read again very carefully, you will see that I modified
> permissions AFTER I noticed they were messed up. Ok?

I tried to point out that your definition of "messed up" is the opposite
of Andy's.  To you, the default permissions provided by setup.exe are
messed up.  To Andy, the permissions you created are messed up.  I hope
that clarifies things.

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

Yes, the more I read, the more I come to believe that the disconnect
here is in the definition of correct and acceptable permissions.  Your
definition differs from that of the Cygwin developers.  It's good that
your permissions changes worked for you, but it's possible that they
won't work for everyone.  A better description of your original problem
as well as how your proposed solution addresses that problem would allow
for a more productive discussion.

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

Your answer was simply an assertion that there possibly was and may
still be something wrong with the permissions handling under Cygwin, but
that you also haven't confirmed that recently.  The details really would
be helpful and likely necessary if you would like to have your patch
accepted by the maintainers of setup.exe.

The only other option is to independently maintain your patch and
rebuild your version of setup.exe any time the upstream version changes.
 This won't help most users, though, because they will either not know
about your patch or not care to build their own setup.exe without having
any evidence of an existing problem and assurance that your change
doesn't introduce other problems.

If you're satisfied with your solution, so be it, but you could pretty
quickly gather the necessary details for a bug report by performing a
second installation of Cygwin into a new directory and reporting the
flawed permissions.  That could lead to the acceptance of your patch or
something similar to the benefit of everyone.

-Jeremy

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