delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2001/05/31/14:09:36

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 31 May 2001 14:09:32 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: [RFD]: Egor's proposal for a Cygwin server process
Message-ID: <20010531140932.F23914@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20010531124452 DOT G1870 AT cygbert DOT vinschen DOT de> <48146951254 DOT 20010531164356 AT logos-m DOT ru> <20010531151226 DOT I1870 AT cygbert DOT vinschen DOT de> <192151639946 DOT 20010531180204 AT logos-m DOT ru> <055e01c0e9da$dc2812d0$0200a8c0 AT lifelesswks> <20010531170820 DOT N1870 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
User-Agent: Mutt/1.3.11i
In-Reply-To: <20010531170820.N1870@cygbert.vinschen.de>; from vinschen@redhat.com on Thu, May 31, 2001 at 05:08:20PM +0200

On Thu, May 31, 2001 at 05:08:20PM +0200, Corinna Vinschen wrote:
>On Fri, Jun 01, 2001 at 12:06:16AM +1000, Robert Collins wrote:
>> From: "egor duda" <deo AT logos-m DOT ru>
>> > CV> As I wrote in my previous mail, it's essential to be sure about
>> > CV> the process which calls the server. Faking of pid, uid and gid
>> > CV> must not be possible!
>> >
>> > something similar was done in my cygserver via
>> > ImpersonateNamedPipeClient(). that's a clear benefit of named pipes
>> > before shared memory.
>> 
>> This is where I'll pop up and say...
>> COM provides benefits here: AFAIK it's got impersonation capabilities
>> for NT, and AFAIK degrades gracefully on 9x.
>
>Hmm, personally I would prefer using a Win32 interface like the
>above (named pipes on NT, shared memory on 9x). Security doesn't
>matter on 9x and the low level interfaces are typically faster
>and (from my point of view) easier to understand. Anyway, if we
>agree to use COM I wouldn't step back.

Are we thinking about making this server able to maintain multiple
platforms?  I think it could possibly be useful to have a single
setuid server running in an NT domain.

Or maybe that's far into the future...

I have a book on COM sitting around somewhere.  I wonder how much
overhead that would add to the Cygwin DLL, though.

Also, I don't know if this has already been mentioned or not but
we also have to make sure that cygwin works ok without the server.
Maybe that means that ttys are not a good candidate for the server
because they are a heavily used feature and we don't want to limit
functionality.

cgf

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019