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: Tue, 31 Oct 2000 18:15:20 -0500 From: Christopher Faylor To: Christopher Faylor Subject: Re: [RFD]: Execute permission for DLLs? Message-ID: <20001031181520.A31409@redhat.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: Christopher Faylor References: <39FEA32B DOT 58D3518F AT cygnus DOT com> <20001031122426 DOT A27656 AT redhat DOT com> <16141549765 DOT 20001031225555 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <16141549765.20001031225555@logos-m.ru>; from deo@logos-m.ru on Tue, Oct 31, 2000 at 10:55:55PM +0300 On Tue, Oct 31, 2000 at 10:55:55PM +0300, Egor Duda wrote: >i've understood it a bit differently. i think Corinna wants to turn >executable bit on when _creating_ tar file on "bad" system which >do not support ntsec, not when unpacking it on ntfs+ntsec system. >Turning executable permissions on when creating dll is solution too, >but for which user will you turn in on? for everyone? i don't think >it's a right thing from security point of view. for owner and group? >then you won't solve original problem. Actually, Corinna wanted to have cygwin always consider a .dll extension as executable. I've actually generated this so that if cygwin detects the executable magic number in the first two bytes of the file it will be considered executable. That means that a.out files will also appear to be executable. cgf