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: Tue, 23 Mar 2004 13:26:55 +0100 From: Corinna Vinschen To: "'cygwin AT cygwin DOT com'" Subject: Re: sshd debugging Message-ID: <20040323122655.GA14240@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: "'cygwin AT cygwin DOT com'" References: <200403230716 DOT 34187 DOT dcorbin AT machturtle DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403230716.34187.dcorbin@machturtle.com> User-Agent: Mutt/1.4.2i On Mar 23 07:16, David Corbin wrote: > I have sshd up and running as a service. I can ssh into the box if I type a > password, but I do have a public-key/private-key installed that it doesn't > seem to recognize. (If you want to recommend a solution to this problem, > please do - it's the real problem). The keys are probably not readable by SYSTEM. Use ssh-user-config as the affected user. The script sets the permissions correctly. > When I have this problem on linux, I usually launch sshd in non-daemon mode > with some debugging flags on a different port. When I try to do this with > cygwin, it says that it can't read the host key and quits. (the host key is > a 0600 and owned by SYSTEM). How can I do this? When I do this, I'm running under my own account and change owner of the files beforehand: chown MyAccount /var/empty /etc/ssh* But that will mostly not help when debugging permission problems with key files. And of course you must remember to revert ownership afterwards. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer 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/