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 Message-ID: <00ca01c4c05e$673a4f70$e6ec6f83@robinson.cam.ac.uk> From: "Max Bowsher" To: "Christopher Cobb" , "D N" , References: <20041101214812 DOT 67C7A4BE64 AT ws1-1 DOT us4 DOT outblaze DOT com> Subject: Re: ssh expect on Cygwin Date: Mon, 1 Nov 2004 22:01:49 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ X-Cam-AntiVirus: No virus found X-Cam-SpamDetails: Not scanned X-IsSubscribed: yes Note-from-DJ: This may be spam Christopher Cobb wrote: > ----- Original Message ----- > From: "D N" > To: ccobb AT email DOT com, cygwin AT cygwin DOT com > Subject: Re: ssh expect on Cygwin > Date: Sun, 31 Oct 2004 17:55:13 +0000 > >> >>> Since passwordless authentication is broken on many cygwin systems I >>> use, I >>> end >>> up using the following expect script (more frequently that I would >>> like). >> >> Are you sure you cant just fix the passwordless login? >> >> I have cyg on 5 different systems - works like a charm! I use keychain to >> manage the keys. > > I have probably a dozen servers which have ssh on it. Although I have > passwordless authentication working on many of them, I cannot get it > working > on one of my main servers. > > I would love to get this working. In fact, I am setting up SVN over ssh > and > I would really love to get rid of the passwords. But there are some > systems > where I can just not get passwordless authentication over ssh working. > > This particular system is in use and I cannot, for example, arbitrarily > reboot it. But short of that, I am willing to provide any troubleshooting > assistence to anyone who thinks they can get to the bottom of this. > > Interestingly enough, between my system and this server, I can get it > working > in one direction (from server to my system), but not the other (from my > system to server -- which is the way I really need it). Go figure. The debugging technique with which I have had the most success with in this kind of circumstances is as follows: Run another instance of sshd on a different port, with full debugging enabled to standard error: $ sshd -Dddde -p 22222 You may well have to fiddle with permissions of the host keys and config files to get this running. Now, try a pubkey login to this alternate sshd. Somewhere in the (copious) debug output, there is usually a clue to why the authentication is failing. NB: In debug mode, sshd will terminate after 1 connection attempt. You will have to restart the alternate sshd each time you want to run another test. Max. -- 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/