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 Date: Thu, 12 May 2005 09:47:43 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Permissions problem mounting NFS shares from Cygwin sshd Message-ID: <20050512074743.GA20217@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050510190317 DOT GB27244 AT thsi DOT org> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050510155711 DOT 09ccf2e8 AT pop DOT prospeed DOT net> <20050510214311 DOT GC27244 AT thsi DOT org> <20050511162049 DOT GB14391 AT thsi DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050511162049.GB14391@thsi.org> User-Agent: Mutt/1.4.2i On May 11 12:20, Chip Olson wrote: > sshd : PID 1364 : starting service `sshd' failed: execve: 1, Operation > not permitted. > > Which tells me Administrator doesn't have the privileges to start > sshd. What does the event log show? In any case, you should not only check permissions on sshd.exe, but also on all files which are accessed by sshd. The general rule is that all these files must be owned by the user running sshd. In your case Administrator. If I'd want to run sshd under another account for testing purposes, I'd do this: $ chown /etc/ssh* /var/empty You should also have another look into the permissions of the private host keys. They should be very strong: $ chmod 600 /etc/ssh_host*key Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/