From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4158 invoked by alias); 18 Apr 2002 08:55:51 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 4109 invoked from network); 18 Apr 2002 08:55:48 -0000 Received: from unknown (HELO cygbert.vinschen.de) (217.81.218.59) by sources.redhat.com with SMTP; 18 Apr 2002 08:55:48 -0000 Received: (from corinna@localhost) by cygbert.vinschen.de (8.11.6/8.9.3/Linux sendmail 8.9.3) id g3I8tkj25321 for cygwin@cygwin.com; Thu, 18 Apr 2002 10:55:46 +0200 Date: Thu, 18 Apr 2002 01:57:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: will bash honor the suid bit or not? Message-ID: <20020418105546.B24938@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i X-SW-Source: 2002-04/txt/msg00933.txt.bz2 On Wed, Apr 17, 2002 at 06:56:08PM -0700, Richard Troy wrote: > [...] First of all, it's not bash but the OS (here Cygwin) which would have to care for the suid bit. Second, the suid bit is available with ntsec on NTFS file systems but for now it's *only* available as a flag. It has no effect! The implementation of suid under Win32 requires a running daemon with special permissions (running under SYSTEM account, that is) which can start a process under a different user account on behalf of the calling process. The daemon already exists but the suid functionality isn't implemented yet. It requires a person with a lot of time, actually... 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/