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: <430B0B47.8040903@wuerfel-datentechnik.de> Date: Tue, 23 Aug 2005 13:40:55 +0200 From: Lars Wuerfel User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Lapo Luchini Subject: Re: openssh v2 public-key problems? References: <430AF21F DOT 3030107 AT lapo DOT it> In-Reply-To: <430AF21F.3030107@lapo.it> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Lapo Luchini schrieb: > 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". [...] > debug1: identity file /home/lapo/.ssh/id_rsa type -1 > debug3: Not a RSA1 key file /home/lapo/.ssh/id_dsa. > debug2: key_type_from_name: unknown key type '-----BEGIN' Is it possible that your id_dsa is not in OpenSSH format? OpenSSH Public keys for ssh-2 protocol look like this: ssh-rsa herecomesthekey... or ssh-dss herecomesthekey... Whereas, for ex., SSH Secure Shell keys for ssh-2 protocol look like this: ---- BEGIN SSH2 PUBLIC KEY ---- herecomesthekey... ---- END SSH2 PUBLIC KEY ---- Just an idea - Lars -- 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/