From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13712 invoked by alias); 18 Jul 2008 12:07:59 -0000 Received: (qmail 13699 invoked by uid 22791); 18 Jul 2008 12:07:59 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 18 Jul 2008 12:07:41 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id EAE6F6D42F1; Fri, 18 Jul 2008 14:09:34 +0200 (CEST) Date: Fri, 18 Jul 2008 12:07:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: New Cygwin 1.7.0-18 in release-2 Message-ID: <20080718120934.GB24731@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20080717155516.GC5675@calimero.vinschen.de> <487FE13C.4020908@byu.net> <20080718073440.GA22938@calimero.vinschen.de> <20080718075451.GB22938@calimero.vinschen.de> <20080718080953.GD22938@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080718080953.GD22938@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-07/txt/msg00069.txt.bz2 On Jul 18 10:09, Corinna Vinschen wrote: > On Jul 18 09:54, Corinna Vinschen wrote: > > On Jul 18 09:34, Corinna Vinschen wrote: > > > On Jul 17 18:18, Eric Blake wrote: > > > > Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading > > > > to the new cygwin1.dll today, I'm now suffering from an inability to > > > > modify files on a shared drive on my work machine. I can create empty > > > > files and remove existing files just fine, but get access denied on any > > > > attempt to change contents. The -1 for owner and group looks fishy as > > > > well. > > > > > > Drive U is apparently a Samba drive. Is that in a Windows domain? > > > If not, try the noacl mount option. It's equivalent to what was > > > CYGWIN=nosmbntsec before. > > > > Hmm, I can reproduce it and now that I see it myself I can see how > > this is a problem with cygdrive mounts. > > > > I assume the best way to handle this would be to set Samba drives to > > noacl by default, right? > > OTOH, I can't choose different mount options for different per cygdrive > mounted drives. All cydrives share the same options. How should we > solve that? I hope that doesn't mean we still need the global > (no)smbntsec option... For a start, I don't think we have to go back to smbntsec. The real problem is exactly what I describe in the comment in fhandler_base::open(). Apparently, creating the file and sending the security descriptor to the server is a two step approach. So Samba creates the file first, and then, afterwards, Windows sends the request to change the security descriptor of the file. Now Samba can't map SID->uid and returns STATUS_ACCESS_DENIED. But there seems to be no knowledge that the two actions are actually one system call in Windows. So Samba doesn't remove the file, but still, NtCreateFile failed. Bummer. I have a local workaround which I'll apply in a minute. However, I never really understood why the mapping from the Windows SID to the UNIX user fails, even though the user has been successfully authenticated before. I have written a clueless mail to the samba developers list. Maybe they can enlighten me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat