X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 14 May 2009 21:22:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7 setup question Message-ID: <20090514192223.GF21324@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) 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 May 14 10:38, Karl M wrote: > > Hi All... > > In the recent setup discussion, there was objection to administrators.none as the default for setup to use. I'm not suggesting any changes, just asking questions for my own understanding. > > Would administrators.none cause any security issues on an install? Probably not, except that all local users are member of the None group. If file are created with 775 or 664 permissions (which hopefully no package uses), then every local, authenticated user can change the file. > Is setup expected to eventually run postinstall scripts as administrator.administrators instead of administrators.none? It's not running scripts as administrators.none, it's running them as user.users-primary-group. That's "None" for all local accounts. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/