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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040609132931.03256eb0@pop.prospeed.net> X-Sender: Date: Wed, 09 Jun 2004 13:35:10 -0400 To: prosolutions AT gmx DOT net, cygwin AT cygwin DOT com From: Larry Hall Subject: Re: Cannot ssh: "Connection reset by peer" error when connecting In-Reply-To: <20040609173155.GA22738@think.alaya.net> References: <1897 DOT 1086795385 AT www24 DOT gmx DOT net> <20040609173155 DOT GA22738 AT think DOT alaya DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 01:31 PM 6/9/2004, you wrote: >So wrote Igor Pechtchanski on Wednesday, the 09. June 2004: >> Date: Wed, 9 Jun 2004 13:13:37 -0400 (EDT) >> From: Igor Pechtchanski >> To: Web Solutions >> Subject: Re: Cannot ssh: "Connection reset by peer" error when connecting >> cc: cygwin AT cygwin DOT com >> >> On Wed, 9 Jun 2004, Web Solutions wrote: >> >> > Freshly installed cygwin on a Windows 2000 (german) system with Service Pack >> > 4 installed. After installation I run ssh-host-config and say "yes" to >> > privilege separation, use "tty ntsec" options, and install it as a service. >> > I then start the service. I login to the cygwin shell and run >> > ssh-user-config. >> > >> > When running ssh-user-config I always only create an RSA2 key. I have tried >> > creating RSA and DSA2 keys but they make no difference and the errors are >> > the same. >> > >> > For the sake of providing as much information as possible I am going to >> > paste the output of 3 different ssh -vvv sessions below. To quickly jump >> > from one to the other just do a find for "SESSION ONE" "SESSION TWO" or >> > "SESSION THREE" >> > >> > This first session: if I create the RSA2 key without a password I am >> > successfully able to connect from localhost: >> > >> > =========SESSION ONE====================================================== >> > OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 >> > [snip] >> > Last login: Wed Jun 9 17:12:12 2004 from 127.0.0.1 >> > >> > >> > =========END SESSION ONE================================================= >> > >> > This next session is an unsuccessful connection attempt with the same user >> > config as before (RSA2 only) except using a password. The session fails: >> > >> > =============SESSION TWO================================================== >> > OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 >> > [snip] >> > Write failed: Connection reset by peer >> > >> > =========END SESSION TWO================================================== >> > >> > This last session is trying to log in from a remote box, (RSA2 set to use >> > password): >> > >> > =============SESSION THREE================================================ >> > >> > OpenSSH_3.8.1p1 Debian 1:3.8.1p1-4, OpenSSL 0.9.7d 17 Mar 2004 >> > [snip] >> > Read from socket failed: Connection reset by peer >> > >> > ============END SESSION THREE============================================= >> > >> > finally, here is the sshd_config: >> > [snip] >> >> Does help? >> Igor >> -- > > > >Interestingly I saw that post just before making my posting here. That >was the last attempt I made to fix it. I tried to chown SYSTEM.SYSTEM >.ssh/* which had no effect whatsoever on the ownership. This user also has full administrative rights. > >Here is the directory listing for /home/user/.ssh: > >total 4 >drwxr-xr-x 2 user Kein 0 Jun 9 17:11 . >drwxr-xr-x 3 user Kein 0 Jun 9 16:09 .. >-rw-r--r-- 1 user Kein 225 Jun 9 17:11 authorized_keys >-rw-r--r-- 1 user Kein 887 Jun 9 17:11 id_rsa >-rw-r--r-- 1 user Kein 225 Jun 9 17:11 id_rsa.pub >-rw-r--r-- 1 user Kein 447 Jun 9 17:12 known_hosts > > >However, given that they are all mode 644 I would think that would be >enough. I've also seen this thread >http://archive.erdelynet.com/ssh-l/2001-06/msg00057.php which indicates >644 should be enough (what I would also tend to think). Also, given the fact that you haven't set "StrictMode" in your sshd_config to "yes", this shouldn't matter. I think you really want to look at the debugging info from sshd. The fact that pubkey authentication works fine without the password but not with suggests to me that there's a problem with the password you're using or your public keys aren't in sync on both machines. You could also look at that before/after viewing the output debug info from sshd. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/