Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 15 Jul 2002 11:25:57 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Permission denied on a windows share Message-ID: <20020715112557.E6932@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.2.20020713194509.02bb9210@pop3.cris.com> <5.1.0.14.2.20020713204337.02acf938@pop3.cris.com> <5.1.0.14.2.20020713220237.02acf568@pop3.cris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Sun, Jul 14, 2002 at 10:44:58AM -0700, Jehan wrote: > What I don't understand is why cygwin doesn't rely on Windows. For what It should. > I know of ntsec, it sets the permissions/ownership of files. It also > read them so "ls -l" show correct permissions (as much as possible > knowing that not all Windows permissions map to Unix). > But once their are set, then Windows should be able to take care of > denying/allowing access accordingly. Why would cygwin need to do more > security checking than Windows does? Why would cygwin deny me write > access to a file when I can do it with any other Windows application? It shouldn't. If the situation is *actually* as you describe it, then there's a bug in Cygwin. However, this requires some debugging in the environment in which this happens... yours. Perhaps an strace of the failing call helps. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/