Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sun, 3 Nov 2002 13:04:37 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Solving ntsec problems? Message-ID: <20021103180437.GA19854@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Pierre did you say that you had some patches which helped alleviate the ntsec problems that people are complaining about? I think we definitely need to add some logic to a postinstall script for setup so that executables are correctly chmod'ed and directories have the proper permission. It would be possible to kludge something along the line of _update_info_dir which gets run every time a package is installed to update /bin /usr/sbin, etc. It would add noticeably to the amount of time taken by setup as it exits, though. I just did a: cd / find bin lib usr etc -name '*.exe' | xargs chmod a+x and it took 27 seconds. That was after messing around with the find command so some of the files/directories were probably already in "cache". This is on my dual PIII 733MHZ system. I don't think we want to add ntsec awareness to setup.exe unless we want to make setup installation a two step process where the setup tar extraction relies on a cygwin DLL. It would be nice to be able to rely on the permissions in the installation tar files being properly preserved on extraction. Anyway, while 1.3.14 seems to have solved some problems, I'm still concerned by the number of people struggling with ntsec issues. I'd like to start taking active steps to solving these problems. FWIW, I'll probably release a 1.3.14-2 with the cygpath changes today. cgf