X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:to:message-id:subject :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=pDTR+hnHMG2updXOANqnvrLGuLxYh5ojekhSELUxGRimHDZK31nZH lSDohx67LvSefGrXFf6Qp0ba5x6gJH2tuBQr7Vq3WPAmEiX9XlIFjzFQujNE25RG lVn7PfvrG00ieIEsTvJ6LuNEu8912URG5AW+wRqpE/cV4yLXvPZOFA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:to:message-id:subject :mime-version:content-type:content-transfer-encoding; s=default; bh=oovwUcDebUK/Xa7Qd8uMhFFe1dk=; b=UcesPLQ1ospoHz9pbUUlg0cgm/E/ PYg67ENcPgpEAlgOc998pTMuLmJfAxfA3eQTBtxsdnA4yWp5u65ufN9DFAWjJRFq /+RPdzqh+TpPkUEciHzgczRUq/tFgZsyJIN8hKo+yG5+KaH9JbaRVx1iFPbYbHTB 5L3CCBM8VLVr0Hg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: nm9-vm6.bullet.mail.gq1.yahoo.com Date: Mon, 7 Sep 2015 12:45:10 +0000 (UTC) From: Zdzislaw Meglicki Reply-To: Zdzislaw Meglicki To: "cygwin AT cygwin DOT com" Message-ID: <314795175.1838495.1441629910506.JavaMail.yahoo@mail.yahoo.com> Subject: Re: Sshd behaving strangely... MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >> Please teach your mail agent to not break threading. Sorry for this. Yes, this particular mailer is really bad, I'll have to re-register with the Cygwin mail list from a better one. >> This is a different issue, judging from the error message. >> [...] >> A verbose log of the same connection from both server >> and client may help. I've attempted a connection from another account on the machine from which I could not do so previously, with ssh -v and... it worked! I made a successful connection. So, then I went back to the account from which I could not connect, ran ssh -v and I got the following: [...] debug1: Offering RSA public key: /home/[user_name]/.ssh/id_rsa Connection closed by [ip_number] Aha! So it's my old RSA key that's the culprit here. I removed it and this time the connection worked just fine! In summary, it appears that it all works as it ought to right out of the box. I configured sshd on the target machine with the "-y" option, which, I presume, builds a default server configuration. My only suggestion would be that, if the connection is refused the reason for refusal should perhaps be printed back to the user, even without the -v option. Many thanks for your help. Zdzislaw (Gustav) Meglicki Indiana University -- -- 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