From owner-freebsd-current  Tue Mar  7 10: 4:43 2000
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 721C537BCB6; Tue,  7 Mar 2000 10:04:41 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA06295;
	Tue, 7 Mar 2000 10:04:40 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id KAA89683;
	Tue, 7 Mar 2000 10:04:39 -0800 (PST)
	(envelope-from jdp@polstra.com)
Date: Tue, 7 Mar 2000 10:04:39 -0800 (PST)
Message-Id: <200003071804.KAA89683@vashon.polstra.com>
From: John Polstra <current@freebsd.org>
To: kris@hub.freebsd.org
Subject: Re: ssh strangeness in -current...
In-Reply-To: <Pine.BSF.4.21.0003061451070.83999-100000@hub.freebsd.org>
References: <Pine.BSF.4.21.0003061451070.83999-100000@hub.freebsd.org>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <Pine.BSF.4.21.0003061451070.83999-100000@hub.freebsd.org>,
Kris Kennaway  <kris@hub.freebsd.org> wrote:
> 
> Ahh, so you can use the OpenSSH client to connect to some servers, but not
> the F-Secure one? That would definitely be a bug you should report to the
> OpenSSH developers.
> 
> Is anyone else in the position to test this?

In the past I have had interoperability problems between F-Secure
and the open source versions of ssh.  But the cause then was simply
that the F-Secure keys were too long (> 1024 bits) for ssh's rsaref
to cope with.

John


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message