Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: ACLs getting reset after gunzip
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Sun, 23 Feb 2003 17:59:30 -0800
Message-ID: <618AE5310A50754A8478629F7A5EB1377AD78C@ngaio.levlin.com>
content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Jonathan Levine" <jon AT levlin DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h1O1xhW27324

Hi.

I'm having a problem with cygwin's g(un)zip.exe and NTFS ACLs.

Here's what I'm seeing:
1. Set a custom ACL for a directory on an NTFS volume (in my case, I
have limited access to a directory to the Administrator group and a
custom group I created, and removed the Everyone group), 

2. Copy a .gz file into the directory 

3. Verify that the .gz file has the same ACLs as the directory 

4. gunzip the file

OBSERVE:The new (gunzipped) file now has a very strange set of new ACLs
-- often the Everyone group is re-added, along with my own account, and
the Administrator permissions are damaged (sometimes "Full Control" is
removed, etc)

Reversing the process has the same effect, i.e.

1. Set a custom ACL for a directory on an NTFS volume (in my case, I
have limited access to a directory to the Administrator group and a
custom group I created), 

2. Copy a .file into the directory 

3. Verify that the .file has the same ACLs as the directory 

4. gzip the file

OBSERVE: And the .gz file has a similarly strange set of ACL's.

I have tried this with CYGWIN=ntsec set and unset.  Also, if it helps,
I'm running g(un)zip from a CMD.EXE window command line.

Also note that using native Windows g(un)zip.exe (from the www.gzip.org
site) produces the expected results, where the new gzipped/gunzipped
file has the same permissions as the parent directory.

Thanks for your help in advance.

Jonathan

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/