[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

SSH2 packet too long error



After upgrading my maching to woody (After many tips on x-config from
other users--thanks) I decided to go from ssh to ssh2 protocol, since
the mail server at work uses this. It works fine and I can connect to
the server, use scp, etc. 

Now I want to use sshd2 to login to my machine remotely. I edited
/etc/inetd.conf to include

ssh             stream  tcp     nowait  root    /usr/sbin/sshd  sshd -i
I also edited hosts.allow to include:
sshd            : ALL   : allow
sshdfwd-X11     : ALL   : allow
sshd1           : ALL   : allow
sshd2           : ALL   : allow
So now the sshd2 port starts up when I reboot. And I can login using a
public key I generated remotely and copied over(I also edited the
authorization and identification files appropriately on both ends). It
accepts the passphrase just fine, but then I get the following error:
warning: Authentication failed.
debug: client_disconnect: Protocol error: packet too long: -1364331183.
debug: Ssh2/ssh2.c:76: locally_generated = TRUE
warning: 
Disconnected; protocol error (Protocol error: packet too long:
-1364331183.).
debug: uninitializing event loop

I've looked around, one suggestion is to configure ssh2 without
tcp-wrappers (--with-libwrap=no). I have libwrap-0 installed as well, if
that matters.
The ssh.com FAQ suggests changing the encryption to Blowfish, but the
ssh-keygen2 I have doesn't support this. Is the debian woody ssh2
configured with or without libwrap? Should there be another
ssh2-nolibwrap distribution, or is there another way to work around
this. 

Also, I've tried connecting without the inetd.conf line (I  get an error
that there is no TCP/IP connection). I also tried changing the line from
sshd to sshd2, but the problem is the same. I had ssh on woody here
before without a problem.

 

Any hints??? 
Thanks,
Glen


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: