X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <24505901.post@talk.nabble.com> Date: Wed, 15 Jul 2009 14:26:01 -0700 (PDT) From: Chap Harrison To: cygwin AT cygwin DOT com Subject: Re: OpenSSH login failing thru PuTTY/plink In-Reply-To: <20090715201305.GA5182@OpenWrt> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <24500041 DOT post AT talk DOT nabble DOT com> <20090715201305 DOT GA5182 AT OpenWrt> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Jurriaan Kalkman wrote: > > any messages in the ssh logs on the servers? Any difference if you run > sshd with debug on on the servers? > This probably isn't what you mean, but -- I looked in /var/log/. sshd.log is length 0 and hasn't been touched in several weeks. The only file with a current modification timestamp is lastlog, which contains nothing of interest (mainly binary zeroes). To activate sshd debugging, I used the Windows Computer Management > Services panel and gave '-d 5' as a start parameter; started the sshd service, attempted a login, stopped the service, and looked at sshd.log. It was still zero length. So - what must I do to get ssh logging and useful sshd debugging information? Best regards, Chap -- View this message in context: http://www.nabble.com/OpenSSH-login-failing-thru-PuTTY-plink-tp24500041p24505901.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple