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: Mon, 10 Sep 2001 21:49:41 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Eliminate cygwin_getshared? Message-ID: <20010910214941.A8638@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i On Tue, Sep 11, 2001 at 11:33:51AM +1000, Robert Collins wrote: >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> Sent: Tuesday, September 11, 2001 10:18 AM >> To: cygwin-developers AT cygwin DOT com >> Subject: Eliminate cygwin_getshared? >> >> >> I was just perusing shared.cc and came across this ill-begotten >> function. It's cygwin's answer to eliminating >> security-through-obscurity. >> >> Is anyone aware of a use for this function? I can't think of any >> reason to export a pointer to cygwin's shared memory area. > >I can. That _might_ allow us to get cygipc to piggy back on cygwin >without becoming part of the kernel. It wouldn't be any more available >to your proprietary customers than it is now, but I don't see that being >an issue (it's a LGPL not GPL IIRC?). In that case, we can invent an interface for dealing with that. Exposing the shared memory for anyone in the world to use, doesn't seem like the way to accomplish this. cgf