Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: X-Originating-Email: [mike_disbrow AT hotmail DOT com] X-Sender: mike_disbrow AT hotmail DOT com From: "Mike Disbrow" To: cygwin AT cygwin DOT com Subject: Re: Renaming Cygwin DLLs Date: Thu, 06 Jan 2005 14:09:13 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 06 Jan 2005 20:10:10.0277 (UTC) FILETIME=[B94C4150:01C4F42B] >On Wed, Jan 05, 2005 at 03:58:39PM -0600, Mike Disbrow wrote: > >I'd like to build the supporting Cygwin DLLs to be renamed to something > >other than cyg*.dll (e.g. cygwin1.dll to foo.dll), what is the best > >way to build the DLLs with different names? > >May I ask why you want to do this? I can't think of any valid reason to >rename the DLL which would not involve trying to mask the existence of >Cygwin. And, I can't think of any reason for doing that which does not >involve either bypassing Cygwin's GPL or trying to take credit for a DLL >which you didn't develop. > The motive isn't that sinister. We'll be deploying Cygwin's X Server to users and don't want the users to know whose X Server we're using. In fact, we're doing all we can to hide the fact that the application they're using is running through X. By changing the dll names we hope to make it a little harder for someone to determine we're using Cygwin's X Server so they don't get the source, and modify it in some malicious way. - Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/