X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A807316.2070103@gmail.com> Date: Mon, 10 Aug 2009 20:20:54 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [1.7] cygwin allows writing to readonly files References: <20090810132515.GP3204@calimero.vinschen.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Alexey Borzenkov wrote: > On Mon, Aug 10, 2009 at 8:11 PM, Alexey Borzenkov wrote: >> Anyway, it means there is a bug in perl, because on Linux: > > On second though, it is actually bug in Cygwin. Programs and libraries expect > superuser behavior only when user id is zero, which is clearly not the case > in Cygwin 1.7. http://www.opengroup.org/onlinepubs/000095399/xrat/xbd_chap03.html > Superuser* > > This concept, with great historical significance to UNIX system users, has > been replaced with the notion of appropriate privileges. This would seem to imply that it is permitted for there to be users other than uid 0 with "appropriate" privileges. Programs should not be trying to second-guess the OS about the privs of a uid, they should ask the access() function and find out. cheers, DaveK -- 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