This is the mail archive of the
mailing list for the Cygwin project.
RE: [ANNOUNCEMENT] (last?) TEST RELEASE: Cygwin 1.7.35-0.5
- From: "Habermann, David (D)" <DAHabermann at dow dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Fri, 27 Feb 2015 18:03:07 +0000
- Subject: RE: [ANNOUNCEMENT] (last?) TEST RELEASE: Cygwin 1.7.35-0.5
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is 220.127.116.11) smtp dot mailfrom=DAHabermann at dow dot com; cygwin.com; dkim=none (message not signed) header.d=none;
- References: <announce dot 20150227175205 dot GP11124 at calimero dot vinschen dot de>
> Since Cygwin 1.7.34, chmod does not always affect the POSIX permission
> mask as returned by stat(2) or printed by ls(1), due to the improved
> POSIX ACL handling. As a temporary workaround, chmod now checks if
I'm a neophyte regarding this ACL handling stuff. Here is my usage model, which probably isn't that far from the model for many Cygwin users: I use Cygwin to process/manage files within the c:\cygwin folder structure, and a very limited number of other folders/files (e.g. /cygdrive/f/backups/...). I don't require complex security on any of these, and would like to keep things very simple.
1) Are there any ACL records that might be inherited from windows down into my structures (I'm in a corporate environment where the corporation "messes" with many things, so our windows might not be "as out of the box").
2) How can I detect/eliminate any ACLs within my folder structures of interest?