DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=HOWSQt9Zm+gxhwEhFRigRNdfZE6Hv
	kiW3GSKbRR9Iln327Hy6LYnOXeMYEo8+ReQWfkkgWHMjZjMuo/ISDD16d8z9hYRF
	v5kE/y8Ouuyacvcnda+wgFDA72ieQdliT701QwSItLziGZ5y5y9DThQ7O/8Fwojo
	xWfgkZXFBhkP3A=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Date: Wed, 8 Apr 2015 05:17:29 -0500
Message-ID: <CAAXzdLUZvdNw_UyOXMa5ozoGuG7zjPnz=rRLELFBoEF8+miZUA@mail.gmail.com>
Subject: setfacl can kill a drive
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

I upgraded to the new Cygwin today, why is this command producing different
permissions? Moreover how do I get it to produce sane results?

    $ cd /cygdrive/c

    $ touch ~/alpha.txt ~+/alpha.txt

    $ ls -l ~/alpha.txt ~+/alpha.txt
    -rw-rwxr--+ 1 Steven None 0 Apr  8 05:06 /cygdrive/c/alpha.txt
    -rw-r--r--  1 Steven None 0 Apr  8 05:06 /home/Steven/alpha.txt

Also I discovered this

    $ setfacl -b /cygdrive/c

After that you get this

    C:\ is not accessible.
    Access is denied.

Luckily this was in a virtual machine. Otherwise, can this be undone? This is
very dangerous, and I feel it should be protected similarly to
"rm --no-preserve-root"

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