delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2012/01/04/09:25:45

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SARE_HEAD_DATE_LONG1
X-Spam-Check-By: sourceware.org
Date: Wed, 4 Jan 2012 15:25:23 +0100 (W. Europe Standard Time)
From: Markus Leuthold <cygwin AT titlis DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin permissions problem on a network drive
Message-ID: <alpine.WNT.2.00.1201041506510.5432@CH01WW6077.corp.ads>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
X-Identified-User: {1045:box507.bluehost.com:leuthold:titlis.org} {sentby:smtp auth 69.89.22.66 authed with ich AT titlis DOT org}
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

--104703717-27306-1325687125=:5432
Content-Type: TEXT/PLAIN; format=flowed; charset=ISO-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Jul  5 10:59, Corinna Vinschen wrote:
> On Jul  5 12:21, Bill Metzenthen wrote:
> > What should I ask the system administrator to change so that cygwin
> > will once again work on this drive?=C2 Perhaps there is some new setting
> > (or an old one which has somehow changed) for cygwin that I have
> > failed to notice?
>
> If you want to discuss this with your admin, the problem is this:  When
> Cygwin 1.7.9 tries to create a file on a filesystem which supports ACLs,
> it requests WRITE_DAC permissions in the open call.  WRITE_DAC is the
> access right you need to create the permission bits in the file's ACL,
> what you see in Explorer under the Security tab.
>
> Now, in some environments, the settings of the shares are so, that this
> right is apparently not granted, even for the creator of the file.
> But, as far as earlier reports go, there seem to be no indication of
> this in the ACL.  As I mentioned above, I experimented with this
> myself, but I have never managed to reproduce this setting on the=20
server.
> So I neither know how this setting looks like, nor if there's a way
> to recognize such a share.
>
>Btw, if you're going to discuss this with your admin, and if you figure
>out what server setting is the culprit, I would be glad if you could
>share the information with us.  It might be a great help in developing
>Cygwin further.
>
>
>Thanks,
>Corinna


Hello Corinna

I've run into the same problem on a DFS filesystem, and I asked our=20
admins about the settings. Please find a screenshot here:=20
http://titlis.org/serversettings.png

The reason why "change permission" (=3DWRITE_DAC) was disabled: Our admins=
=20
don't want to allow "take ownership" to everybody, since in the past users=
=20
managed to set the rights such that even the admins couldn't access the=20
file anymore. Since "take ownership" automatically enables "change=20
permissions", WRITE_DAC is thus disabled too.

hope that helps

best regards, Kusi

PS: your workaround works fine, too




--104703717-27306-1325687125=:5432
Content-Type: text/plain; charset=us-ascii

--
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
--104703717-27306-1325687125=:5432--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019