Re: ssh2 and non-stable
- To: Debian Laptops List <firstname.lastname@example.org>
- Subject: Re: ssh2 and non-stable
- From: brew@theMode.com
- Date: Sat, 24 Feb 2001 10:42:46 -0500 (EST)
- Message-id: <Pine.SOL.4.04.10102241029380.11997-100000@unix01>
- In-reply-to: <20010224151624.D17120@strider>
Heather, Daniel, Drew and list.....
Drew pointed out that ssh2 is the commercial version and only handles SSH2
on it's own. I installed ssh (unstable package ) which is the OpenSSH
version and chose to replace my old config files with the ones in the
package, and it handles both SSH2 and degrades to SSH1 automatically.
Somehow when I thought I'd installed ssh (unstable) before, I guess I
really hadn't, even though I thought the version number changed to 2.x, I
never saw the 'protocol versions 1.5/2.0' in the ssh -V version report
when I checked so it couldn't have been this version.
Live and learn - thanks guys.
> > When I do a ssh -V:
> > ssh: SSH Version 2.0.13
> > Don't know if that is openSSH, but I think so.
> ssh2 is the "commercial" (non-free) version. ssh is the free version (i.e.
> OpenSSH). I got real confused about the difference too. The (commercial)
> ssh author has a point, in his recent complaints about trademark confusion.
> Although really in our case it's Debian that's at fault, not OpenSSH, since
> we're the ones calling the package ssh instead of openssh.
> Anyway, I run ssh from unstable. ssh -V says:
> SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
> Compiled with SSL (0x0090600f).