From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1333383156.33489.YahooMailClassic@web83915.mail.sp1.yahoo.com>
Date: Mon,  2 Apr 2012 09:12:36 -0700
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <a960b604215b40474033ec8e5b586c5e@sp.nv>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [9fans] SSHv2
Topicbox-Message-UUID: 7474b86a-ead7-11e9-9d60-3106f5b1d025

> After patching ndb/cs and running
> nfactotum, I'm still having
> some trouble getting the new ssh to successfully login to a
> remote system:
>
> term% ssh2 openbsd
> The following key has been offered by the server:
> ek=10001
> ...
>
> Add this key? (yes, no, session) yes
> ssh2: dial: handshake failed

Unfortunately, the handshake failed error is something of
a catch-all when something fails in the early negotiation
to set up the connection.  To narrow in on what's happening,
could you first kill all instances of sshtun that are running.
Then run a fresh instance of auth/factotum and don't load
anything from secstore.  Then try ssh again.  If it still
doesn't work, kill sshtun again, and run it manually with
a -d option, then run ssh.  You should get quite a lot of
output to stderr and that will hopefully give us some clue
as to what's happening.

BLS