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: Wed, 18 Apr 2001 15:23:17 +0400 From: egor duda X-Mailer: The Bat! (v1.45) Personal Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <123329292477.20010418152317@logos-m.ru> To: "Robert Collins" CC: cygwin-developers AT cygwin DOT com Subject: Re: handle protection - please comment In-reply-To: <00ba01c0c7f6$530ac1b0$0200a8c0@lifelesswks> References: <20010418120530 DOT Q15962 AT cygbert DOT vinschen DOT de> <00a401c0c7f0$02bb1f30$0200a8c0 AT lifelesswks> <13327115627 DOT 20010418144700 AT logos-m DOT ru> <00ba01c0c7f6$530ac1b0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Wednesday, 18 April, 2001 Robert Collins robert DOT collins AT itdomain DOT com DOT au wrote: >> If you can suggest any other way to pass handles from process A (run >> by user User1) to process B (run by user User2) without having server >> run by administrator, it would be great. RC> Place them in a a list in a shared memory area. That is essentially what RC> kernels do. No process memory access is needed. They _are_ in shared memory area already. Passing handle value (via shared memory area or by other means) from process A to process B is _not_ enough to use it in process B. win32 handles _must_ be duplicated after they were passed from one process to another. i know only 2 things in win32 api which allow using a handle from one process in another -- either inheritance or DuplicateHandle(). If you know some other way, it'd be nice to see the proof-of-concept code. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19