Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Mar 2001 08:20:51 -0600
From:      "Thomas T. Veldhouse" <veldy@veldy.net>
To:        "Jon Nathan" <jon@rupture.net>
Cc:        "Dima Dorfman" <dima@unixfreak.org>, <freebsd-stable@FreeBSD.ORG>
Subject:   Re: OpenSSH 
Message-ID:  <006201c0a57f$7bf35c70$3028680a@tgt.com>
References:  <Pine.BSF.4.21.0103050925390.85816-100000@froody.rupture.net>

next in thread | previous in thread | raw e-mail | index | archive | help
I use it against my FreeBSD 4.2-STABLE -- right now as a matter of fact --
tunneling my SMTP through it.

I use the 2.4 version of the client.

Tom Veldhouse
veldy@veldy.net

----- Original Message -----
From: "Jon Nathan" <jon@rupture.net>
To: "Thomas T. Veldhouse" <veldy@veldy.net>
Cc: "Dima Dorfman" <dima@unixfreak.org>; <freebsd-stable@FreeBSD.ORG>
Sent: Monday, March 05, 2001 8:29 AM
Subject: Re: OpenSSH


> i can confirm problems with at least the ssh.com ssh2 client
> connecting to openssh2.3.0 (4.2-stable).  maybe i have an old version
> of the ssh.com client - i haven't worried a whole lot about it because
> an upgrade is planned for the box with the ssh.com client anyway.
>
> jon@froody:~> which ssh
> /usr/bin/ssh
> jon@froody:~> ssh -V
> ssh: SSH Secure Shell 2.1.0.pl2 (non-commercial version)
> jon@froody:~> ssh w2.chaffee.com
> ssh in free(): warning: chunk is already free.
> warning: Authentication failed.
> warning:
> Disconnected; key exchange or algorith negotiation failed (Key
> exchange failed.).
> jon@froody:~> ssh -v w2.chaffee.com
> warning: Development-time debugging not compiled in.
> warning: To enable, configure with --enable-debug and recompile.
> debug: hostname is 'w2.chaffee.com'.
> debug: Unable to open /home/jon/.ssh2/ssh2_config
> warning: Development-time debugging not compiled in.
> warning: To enable, configure with --enable-debug and recompile.
> debug: connecting to w2.chaffee.com...
> debug: entering event loop
> debug: ssh_client_wrap: creating transport protocol
> debug: Ssh2Client/sshclient.c:1015/ssh_client_wrap: creating userauth
> protocol
> debug: Remote version: SSH-1.99-OpenSSH_2.3.0
> debug: Ssh2Client/sshclient.c:349/keycheck_key_match: Host key found
> from database.
> ssh in free(): warning: chunk is already free.
> warning: Authentication failed.
> debug: client_disconnect: Key exchange failed.
> debug: Ssh2/ssh2.c:77/client_disconnect: locally_generated = TRUE
> warning:
> Disconnected; key exchange or algorith negotiation failed (Key
> exchange failed.).
> debug: uninitializing event loop
> jon@froody:~>
> jon@froody:~> ssh1 w2.chaffee.com
> jon@w2.chaffee.com's password:
> Last login: Mon Mar  5 14:12:13 2001 from froody.rupture.n
> Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
>         The Regents of the University of California.  All rights
> reserved.
> FreeBSD 4.2-STABLE (CHAFFEE) #1: Sat Mar  3 23:01:25 EST 2001
>
> w2.chaffee.com
>
> Stay away from hurricanes for a while.
> jon@w2:~>
>
> -jon
>
> --
> Jon Nathan
> jon@rupture.net
> http://www.rupture.net/~jon/
>
>
> On Mon, 5 Mar 2001, Thomas T. Veldhouse wrote:
>
> >
> > > Not likely, considering it isn't even in -current yet.  There are some
> > > alleged problems with it, especially when interacting with ssh.com
> > > implementations.  I say alleged because while I've seen many
> > > complaints about this on the development list, I've never actually
> > > seen them myself.
> >
> > I have used 2.5.0pl1 with SSH2 client from ssh.com and with the SSH1
client
> > in TeraTerm Pro.  No problems at all.
> >
> > >
> > > Regardless of the last part of the above, however, there's almost no
> > > chance you'll see it in 4.3-RELEASE.  Such things need time to settle
> > > in -current before they're merged.
> >
> > I have to agree that it should settle a bit --- just to make sure stable
is
> > indeed stable.  There has been enough chaos lately.
> >
> > >
> > > Dima Dorfman
> > > dima@unixfreak.org
> > >
> >
> >
> > Tom Veldhouse
> > veldy@veldy.net
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> >
>
>


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006201c0a57f$7bf35c70$3028680a>