X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Date: Thu, 30 Apr 2009 17:05:17 -0500 (CDT) From: Tim McDaniel To: cygwin AT cygwin DOT com Subject: Re: I'd like to have an unreadable file In-Reply-To: <49FA1C44.6020007@cygwin.com> Message-ID: References: <49FA1C44 DOT 6020007 AT cygwin DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 Thu, 30 Apr 2009, Larry Hall wrote: > It's a known fact that Cygwin allows users that are members of the > Adminstrators group access to any file, regardless of its > permissions. Thank you for the quick reply. (Though I find it scary that Cygwin can escalate privileges so very much.) I guess the workaround would be to simply test the script by running as a user who is not in the Administrators group. -- Tim McDaniel, tmcd AT panix DOT com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/