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 From: David Corbin To: cygwin AT cygwin DOT com Subject: Re: sshd debugging Date: Tue, 23 Mar 2004 22:17:22 -0500 User-Agent: KMail/1.5.4 References: <200403230716 DOT 34187 DOT dcorbin AT machturtle DOT com> <20040323122655 DOT GA14240 AT cygbert DOT vinschen DOT de> In-Reply-To: <20040323122655.GA14240@cygbert.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403232217.22146.dcorbin@machturtle.com> On Tuesday 23 March 2004 07:26, Corinna Vinschen wrote: > 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. Thanks. That corrected it. What does it really mean to be readble by "SYSTEM"? I'm fairly savy about unix/windows security, but I'm not sure I have a clue how cygwin manages things. -- David Corbin -- 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/