X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <26280017.post@talk.nabble.com> Date: Tue, 10 Nov 2009 00:44:01 -0800 (PST) From: aputerguy To: cygwin AT cygwin DOT com Subject: Differences between 'ls' permissions *nix vs cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I'm not sure if this is a bug or a feature. But I find the following differences between *nix and cygwin on access permissions of 'ls' Test case: $ mkdir -p dir1/dir2 $ chmod 700 dir1 $ ls -d dir1 dir1 [both Linux & Cygwin] $ ls dir1 ls: cannot open directory dir1 Permission denied [both Linux & Cygwin] $ ls -d dir1/dir2 ls: cannot access directory dir1/dir2 Permission denied [Linux] dir1/dir2 [Cygwin] No acl's beyond the standard ugo posix permissions are set on either system. The Cygwin user only belongs to the 'None' and 'Users' group. In particular, why is a non-privileged Cygwin user able to look over a blocked directory further into a file tree? -- View this message in context: http://old.nabble.com/Differences-between-%27ls%27-permissions-*nix-vs-cygwin-tp26280017p26280017.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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