Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 23 Apr 2002 12:18:37 -0400
From:	Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: The cygwin Server Daemon
Message-ID:	<20020423161837.GB8032@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<FC169E059D1A0442A04C40F86D9BA7600C5ED7 AT itdomain003 DOT itdomain DOT net DOT au> <Pine DOT LNX DOT 4 DOT 33 DOT 0204230800540 DOT 9968-100000 AT fs1 DOT in>
Mime-Version:	1.0
In-Reply-To:	<Pine.LNX.4.33.0204230800540.9968-100000@fs1.in>
User-Agent:	Mutt/1.3.23.1i

On Tue, Apr 23, 2002 at 08:51:24AM -0700, Richard Troy wrote:
>Here's what I envision at this point: _execve() code notices the
>suid/guid bits are set, checks that the file owner is not the caller
>and that the callers group list does not include the files group id,
>and dispatches a message to cygserver.  That message includes the path
>to the image - and does not include the owner.group as a secondary
>guard to security at the cost of having to fetch this information a
>second time.

Just a minor nudge, but the code to look at is undoubtedly in spawn.cc,
specifically the spawn_guts function.  The exec calls are all wrappers
for that function.

cgf

--
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/

- Raw text -