/usr/local, /var and */tmp in c:\Users\Public
Mon Nov 17 14:36:00 GMT 2014
On Sat, Nov 15, 2014 at 1:41 PM, Lee wrote:
> On 11/15/14, Jeffrey Altman wrote:
>> On 11/15/2014 12:55 PM, Lee wrote:
>>>> So, just because I installed Cygwin with my regular user account,
>>> You're doing it wrong. Install Cygwin using an admin account and
>>> regular user accounts are not allowed write access to system
>> This feels really wrong to me. If installing Cygwin under a non-admin
>> account results in a potential security vulnerability, then the
>> installer should be taking that into account.
> I would argue that no, the installer should _not_ take that into
> account. If someone wants to install cygwin under their regular
> userid, why should the installer try to work around that? The files
> are installed with the "correct" permissions if the windows admin has
> an administrator account for doing admin chores & a regular user
> account for doing day to day user tasks.
Because a user who is using a corporate laptop with administrator
accounts locked down would not be able to install Cygwin.
Because a user who is used to having ownership of the files he
installs would become frustrated that he could not remove Cygwin by
simply opening the Windows explorer, picking his way to the Cygwin
root folder, right clicking it and saying Delete.
Because this list would become overrun with queries of why can't I add
a program from an archive to the /usr/bin directory or remove or ...
An install "Only for the user" should not create such locked down
control of the system without asking. Some users tend to know what to
do and what not to do and do not want the extra measures to protect
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin