From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon,  2 Apr 2012 10:39:11 -0400
To: 9fans@9fans.net
Message-ID: <322ae65c1b7233421b92f2e54490cc3c@kw.quanstro.net>
In-Reply-To: <816fa7ab604784c4b52ffad0d9317164@kw.quanstro.net>
References: <a2e41a4ec2e424c89fb48ffdebb96be0@bellsouth.net>
	<a960b604215b40474033ec8e5b586c5e@sp.nv>
	<816fa7ab604784c4b52ffad0d9317164@kw.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] SSHv2
Topicbox-Message-UUID: 745fca36-ead7-11e9-9d60-3106f5b1d025

On Mon Apr  2 10:30:50 EDT 2012, quanstro@quanstro.net wrote:
> On Mon Apr  2 10:28:28 EDT 2012, sl@9front.org wrote:
> > After patching ndb/cs and running nfactotum, I'm still having
> > some trouble getting the new ssh to successfully login to a
> > remote system:
[...]
>
> we're working on it.

i should say this works for me, and nearly everybody, but we
have seen one similar case.  but everyone else on the system
has success.

so the current thinking is tht  there's something in the environment
that's broken.  in fact, i'd recommend moving your keyrings and
other files accessed by ssh or the tunnel out of the way and trying
again.

thanks!

- erik