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 Date: Tue, 23 Aug 2005 13:41:32 +0200 From: Corinna Vinschen To: "[ML] CygWin " Subject: Re: openssh v2 public-key problems? Message-ID: <20050823114132.GP17452@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: "[ML] CygWin " References: <430AF21F DOT 3030107 AT lapo DOT it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <430AF21F.3030107@lapo.it> User-Agent: Mutt/1.4.2i On Aug 23 11:53, Lapo Luchini wrote: > I just installed a new host in my LAN, using the new&shiny > ssh-host-config, using privilege separation and all and (finally!) > getting to use public key authentiucation. > Problem is: using protocol v2 all I get is a "Connection reset by peer" > instead of a "SSH2_MSG_KEX_DH_GEX_REPLY". > > Is that "normal" with the actual degree of support under Windows? No. I'm using the V2 protocol all the time. You should have a look into the syslog if there's some hint. If not, try running sshd on the command line with debug output enabled (-d). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/