Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 15:34:31 +0200 From: Corinna Vinschen To: cygdev Subject: Re: [RFD]: Egor's proposal for a Cygwin server process Message-ID: <20010531153431.L1870@cygbert.vinschen.de> Reply-To: cygdev Mail-Followup-To: cygdev 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> <050601c0e9d3$9d0dea40$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <050601c0e9d3$9d0dea40$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, May 31, 2001 at 11:14:23PM +1000 On Thu, May 31, 2001 at 11:14:23PM +1000, Robert Collins wrote: > ----- Original Message ----- > From: "Corinna Vinschen" > > > As I wrote in my previous mail, it's essential to be sure about > > the process which calls the server. Faking of pid, uid and gid > > must not be possible! > > > > Doesn't that imply that the server must spawn every process? Or at least > be the caller of the win32 to start the process and setup the > process<->server communication channel? Hmm, yes, seems so... if we don't find another way... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.