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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Jason Lunz Subject: Re: Spurious executable bits keep turning up Date: Fri, 11 Jul 2003 19:25:28 +0000 (UTC) Organization: PBR Streetgang Lines: 19 Message-ID: References: X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: slrn/0.9.7.4 (Linux) pechtcha AT cs DOT nyu DOT edu said: > Other than the obvious "chmod 600", you mean? well, sort of. In this case, the full cygwin environment isn't being installed. I'm just using ssh.exe and the cygwin DLL to temporarily set up an ssh tunnel, but ssh complains when the permissions on its key file are too loose. The key file is created when it's unpacked by NSIS. On Win2k, ssh thinks the permissions are OK. on XP, it doesn't. I don't know whether this is due to a difference between how NSIS creates the file on 2K and XP, or whether it's a difference in how cygwin maps the permissions for ssh on the two OSes. I was asking whether there were a workaround for the latter without establishing whether that was actually the problem. :) It turns out that using chmod makes ssh happy under XP, so my problems are solved. thanks. Jason -- 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/