From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Fri, 27 Mar 2015 17:48:15 +0100 Message-ID: From: Rudolf Sykora To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: [9fans] ssh handshake failed Topicbox-Message-UUID: 4b8822dc-ead9-11e9-9d60-3106f5b1d025 Hello, trying to connect from 9atom via ssh (v2) to my linux machine I get: ssh: dial: handshake failed What should I check that might have gone wrong? (The machine is otherwise accessible from other systems via ssh.) Thank you Ruda From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1427475747.85840.YahooMailBasic@web184702.mail.ne1.yahoo.com> Date: Fri, 27 Mar 2015 10:02:27 -0700 From: "Brian L. Stuart" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [9fans] ssh handshake failed Topicbox-Message-UUID: 4b910154-ead9-11e9-9d60-3106f5b1d025 > trying to connect from 9atom via ssh (v2) to my linux machine I get: > > ssh: dial: handshake failed > > What should I check that might have gone wrong? > (The machine is otherwise accessible from other systems via > ssh.) The first thing to check is whether the Linux box is configured to do password auth or just "keyboard interactive" auth. It seems that OpenSSH these days defaults to having real password auth turned off, but keyboard interactive turned on. It's usually implemented so that it looks the same to the end user, but the protocol is different. The SSHv2 implementation does not currently support keyboard interactive. Having said that, I seem to remember that the handshake failed error actually occurs before you get to the auth stage. It's very early in the negotiation when the two sides exchange identities and supported versions. It's possible to run the tunnel with debugging turned on and see what is being exchanged and what is being complained about. Similarly, you might look at logs on the Linux side to see if there's something it's complaining about. BLS From mboxrd@z Thu Jan 1 00:00:00 1970 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----ECX6W521R68GM6XZJE401TH8N0U2RR" Content-Transfer-Encoding: 7bit From: mischief@9.offblast.org Date: Fri, 27 Mar 2015 10:09:18 -0700 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>, Rudolf Sykora Message-ID: <9C9B2F14-8A57-4D6B-96C4-E1E5606E2CC1@9.offblast.org> Subject: Re: [9fans] ssh handshake failed Topicbox-Message-UUID: 4b9be0ba-ead9-11e9-9d60-3106f5b1d025 ------ECX6W521R68GM6XZJE401TH8N0U2RR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I encourage you to try scpu=2E https://bitbucket=2Eorg/mischief/scpu There are binaries available in 9front pkg repos=2E On March 27, 2015 9:48:15 AM PDT, Rudolf Sykora wrote: >Hello, > >trying to connect from 9atom via ssh (v2) to my linux machine I get: >ssh: dial: handshake failed > >What should I check that might have gone wrong? >(The machine is otherwise accessible from other systems via ssh=2E) > >Thank you >Ruda ------ECX6W521R68GM6XZJE401TH8N0U2RR Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable I encourage you to try scpu=2E

https://bitbucket=2Eorg/= mischief/scpu

There are binaries available in 9front pkg repos=2E


On March 27, 2015 9:48:15 AM PDT, Rudol= f Sykora <rudolf=2Esykora@gmail=2Ecom> wrote:
Hello,

trying to connect from 9atom via s=
sh (v2) to my linux machine I get:
ssh: dial: handshake failed
What should I check that might have gone wrong?
(The machine is ot=
herwise accessible from other systems via ssh=2E)

Thank you
Ruda


------ECX6W521R68GM6XZJE401TH8N0U2RR--