This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: /usr/local, /var and */tmp in c:\Users\Public
- From: Warren Young <warren at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 13 Nov 2014 14:09:55 -0700
- Subject: Re: /usr/local, /var and */tmp in c:\Users\Public
- Authentication-results: sourceware.org; auth=none
- References: <81578012-FD3F-4463-BC56-ADB092317DD4 at etr-usa dot com> <CABa6CEkRV=3FY6ZVGrdt--rH3PppwCJRD5poU0L2knv2k2ce_w at mail dot gmail dot com> <25F385A9-3E2D-44FC-998F-D2672F67DFE4 at etr-usa dot com> <m40npq$vrq$1 at ger dot gmane dot org> <ECD073FF-B78C-4D19-8DE1-5F4E390D2495 at etr-usa dot com> <20141113093335 dot GI2782 at calimero dot vinschen dot de>
On Nov 13, 2014, at 2:33 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Nov 12 17:19, Warren Young wrote:
>>
>> I’m not advocating that step so early, but maybe if this breakup does
>> happen, a few years later setup.exe can start applying some strong
>> ACLs to files it writes.
>
> ??? What "strong" ACLs?
The ones that are not there right now. :)
Just to pick a random example:
$ ls -l /bin/ls.exe
-rwxrwxr-x 1 Warren None 116253 Oct 13 10:12 /bin/ls.exe
The same file’s permissions, from Windows’ perspective:
http://etr-usa.com/cygwin/ls-perms.png
So, just because I installed Cygwin with my regular user account, I get permission to rewrite ls.exe. This is not a good thing, if our goal is to make Cygwin work like Linux while working *within* the Windows environment.
IMHO, the way to meet both goals simultaneously is to put programs in c:\Program Files, and to give full-control perms to the local Administrator account in the SAM case, or possibly the domain one in the AD case.
--
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