X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <20090810132515 DOT GP3204 AT calimero DOT vinschen DOT de> Date: Mon, 10 Aug 2009 22:50:00 +0400 Message-ID: Subject: Re: [1.7] cygwin allows writing to readonly files From: Alexey Borzenkov To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. I think that maybe only local administrator account should be assigned user id 0, and that only local administrator should be allowed reading/writing files that it has no access to. -- 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