From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 906 invoked by alias); 2 Jul 2012 16:10:45 -0000 Received: (qmail 888 invoked by uid 22791); 2 Jul 2012 16:10:43 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com) (209.85.217.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Jul 2012 16:10:29 +0000 Received: by lbom4 with SMTP id m4so7989757lbo.2 for ; Mon, 02 Jul 2012 09:10:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding :x-gm-message-state; bh=1s/cBV0k67wmbo0/z78Vs5UsPmQz/PgQgzyFl0Rpc7E=; b=bZVYx7YJtPTlnLYXkaw/enA0nTcPzJP1Yrn0CSxLbJspbr57tBdvBjUInMi5XtoraX W5Zuu6cyrpcqX+iBFHgAqYQFctAqIvHMu6Re49MRKnw0cjZu02a46Uw7poPbu+0Dblov vH+p7h2jZBM5hIlQARhQLrMUFcLpSVxTcEO9s63sE+nC5DYxAiYaxpZ6MD5lJx+0yU2f tgjwahBaNBjcTHaKgKN1cQEFqD4Jri/QAY0iCw5uS3EbSbmsUSUlT9CO94fE0R3aCRXR trnyDb7AEaua/Tl63DnzD01O+eT7mwN1uKnZnaCMdHWRhW88+aYZmIK9s8jLHrOgns71 7ocg== Received: by 10.112.38.161 with SMTP id h1mr6541155lbk.85.1341245427702; Mon, 02 Jul 2012 09:10:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.64.142 with HTTP; Mon, 2 Jul 2012 09:09:47 -0700 (PDT) In-Reply-To: <0260B13BA0AA1A4693F4245FC28FD77705EC62CC1C@CVL-SVR-002> References: <0260B13BA0AA1A4693F4245FC28FD77705EC62CC1C@CVL-SVR-002> From: Richard Gribble Date: Mon, 02 Jul 2012 16:10:00 -0000 Message-ID: Subject: Re: I'm having problems with cygwin 1.7 and ACL handling. To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmraE+td67gpXU9HWppJ9HpgE6a11PR9AibWj0Ag0pbXHxivxwCbEB+poMmTtyUtVEBiZ2y X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-07/txt/msg00016.txt.bz2 This may not work for you, but what I had to do was to mount the drives with the noacl option. This problem first surfaced for me when the server was upgraded from Windows 2003 Standard to Windows 2003 R2 Standard, and was noticeable in RCS where I couldn't check out files because I couldn't create the necessary temp files. I worked on it for several weeks with the IT person, and there was no way we could it to work. The privileges matched precisely (under Windows) - the only way I could do it was to be an administrator (and that wasn't going to happen). Hope this helps, Richard. On Mon, Jul 2, 2012 at 11:56 AM, Mark Lommers wrote: > > Hi, > > I'm having problems with cygwin 1.7 and ACL handling. > > I do some software development and for the software I write I also create= unit tests. Those unit test are run automatically in a cygwin environment = triggered by a build system. Now I'm updating the machines on which the uni= t tests are running, from windows XP to Windows Server 2008 and from cygwin= 1.5 to cygwin 1.7. Since this update some unit tests are failing. > > All the failing unit tests have in common that they do something with ACL: > > For some test we change the access control list like: > > acl.AddAccessRule(new System.Security.AccessControl.FileSystemAcces= sRule(WindowsIdentity.GetCurrent().Name > , System.Security.AccessControl.FileSystemRights.FullControl > , System.Security.AccessControl.AccessControlType.Deny)); > SandboxedDirectory.SetAccessControl(acl); > > Then in the test we try to create a directory inside the sandboxed direct= ory and check that the right exception has been thrown because it shouldn't= be able to do so. > > > On windows XP with cygwin version 1.5 everything was working OK > > Now we are upgrading to windows server 2008 so we also need to update to = cygwin 1.7, the test are starting to fail, because they are able to create = directories in the sandboxed directory. > > I know/read that from cygwin 1.7 cygwin uses mount point with correspondi= ng acl/noacl flags and no longer using the ntsec and nontsec flags in the C= YGWIN environment variable. > > I tried to change the mounting point to set noacl and acl but this didn't= had any effect. > > On the OLD xp machines with cygwin 1.5 the CYGWIN variable was set to non= tsec > > In CMD prompt test run fine. > In a bash prompt test fail. > In a cmd prompt started from a bash prompt test also fail. > > Not running in a cygwin environment is not an option for now! > > Any Idea what to do? > > Regards > Mark > > -- > 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 > -- 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