This is the mail archive of the
mailing list for the Cygwin project.
Re: setfacl can kill a drive
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Steven Penny <svnpenn at gmail dot com>, cygwin at cygwin dot com
- Date: Thu, 9 Apr 2015 00:46:37 +0300
- Subject: Re: setfacl can kill a drive
- Authentication-results: sourceware.org; auth=none
- References: <CAAXzdLUZvdNw_UyOXMa5ozoGuG7zjPnz=rRLELFBoEF8+miZUA at mail dot gmail dot com> <CAAXzdLUgnjfeA=LkrdUp68zHterj5hj5BtLqh0W=TCAn1zPrpQ at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot com
Greetings, Steven Penny!
>> I upgraded to the new Cygwin today, why is this command producing different
>> permissions? Moreover how do I get it to produce sane results?
> I was able to use these command to produce sane results
> $ cd /cygdrive/c
> $ touch bad.txt
> $ setfacl -k .
> $ touch good.txt
> $ ls -l *.txt
> -rw-rwxr--+ 1 John None 0 Apr 8 02:16 bad.txt
> -rw-r--r-- 1 John None 0 Apr 8 02:16 good.txt
> I feel that the default permissions are wrong here. On linux when you create a
> new file with touch, it does not have executable permissions, for good reason.
> This would be a security issue.
Cygwin is not Linux.
And C:\ drive is not a part of Cygwin.
If you really want to destroy your Windows installation, there's easier ways
than meddling with setfacl on the root drive.
With best regards,
Thursday, April 9, 2015 00:45:45
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple