This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: setfacl can kill a drive
- From: Steven Penny <svnpenn at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 8 Apr 2015 16:40:20 -0500
- Subject: Re: setfacl can kill a drive
- Authentication-results: sourceware.org; auth=none
- References: <CAAXzdLUZvdNw_UyOXMa5ozoGuG7zjPnz=rRLELFBoEF8+miZUA at mail dot gmail dot com>
On Wed, Apr 8, 2015 at 5:17 AM, Steven Penny wrote:
> 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.
--
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