[lug] openssh server update

[Hugh Brown]

on my server:


[server]# grep -v "^#" /etc/ssh/sshd_config

Port 22
Protocol 2,1
HostKey /etc/ssh/ssh_host_key
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
KeyRegenerationInterval 3600
ServerKeyBits 768
SyslogFacility AUTHPRIV
LogLevel INFO
LoginGraceTime 600
StrictModes yes
X11Forwarding yes
Subsystem       sftp    /usr/libexec/openssh/sftp-server

[server]# ssh -v localhost
OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090581f
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.1p1


[client]$  ssh -V
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090581f

[client]$ ssh -1 server
Disconnecting: Corrupted check bytes on input.


The windows clients get similar problems.

Hugh

On Mon, 2002-03-11 at 15:40, Jonathan Briggs wrote:
> Did you put Protocol 2,1 in your sshd_config file?  I believe it used to 
> default to Protocol 2,1, but now it defaults to only Protocol 2.
> I believe it still supports version 1 however.
> 
> I just tested it.  Yeah, it supports version 1.  Try fixing your 
> sshd_config file.
> 
> Hugh Brown wrote:
> 
> >I dutifully updated openssh on all of my servers, now as I side result. 
> >I can't connect to them using ssh v1 from putty or from older openssh
> >clients.
> >
> >I get 
> > Corrupted check bytes on input.
> >
> >
> >Or CRC errors on windows.
> >
> >The reason I care is that we are tunneling cvs over ssh which is
> >bouncing through a firewall.  I have a few windows users that rely upon
> >putty and wincvs.  I couldn't get putty to do agent forwarding for
> >sshv2.  If I could get that to work, all of the above is moot.
> >
> >
> >Help.
> >
> >Hugh