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 18:02:04 +0400 From: egor duda X-Mailer: The Bat! (v1.45) Personal Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <192151639946.20010531180204@logos-m.ru> To: cygdev Subject: Re: [RFD]: Egor's proposal for a Cygwin server process In-reply-To: <20010531151226.I1870@cygbert.vinschen.de> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Thursday, 31 May, 2001 Corinna Vinschen vinschen AT redhat DOT com wrote: >> a communication between client and server is restricted to local host >> only, so, i suppose, we can take "mixed" approach -- use named pipes >> on nt/2000 and shared memory on w9x. 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. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19