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 Mar 2004 16:04:08 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: suid bit on executables?
Message-ID: <20040323150408.GT17229@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20040323105820 DOT GB13267 AT cygbert DOT vinschen DOT de> <Pine DOT LNX DOT 4 DOT 33 DOT 0403230654282 DOT 1808-100000 AT denzel DOT sciencetools DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0403230654282.1808-100000@denzel.sciencetools.com>
User-Agent: Mutt/1.4.2i

On Mar 23 07:04, Richard Troy wrote:
> I know
> there's the SSHD code that could serve as an example, but it seems to me
> that it's overkill for what I want [...]

Nope.  There's nothing simpler than utilizing an existing and working
piece of code instead of creating another application with it's entirely
new, own set of bugs.  IMO, using sshd is the way to go.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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