thr3ads.net - openssh unix dev - Bad packet length error [Aug 2003]

If this information is useful, please help other people find it:
Share via:

Hari (E-mail)

2003-Aug-26 01:25 UTC

Bad packet length error

Hi,
I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am
connecting from a ssh client (openssh-2.9p2) on an x86 Linux box.
This works fine for ssh protocol version 1, but am getting the below error
for ssh v2:

Disconnecting: Bad packet length -857542839.

I am also attaching the complete debug traces from sshd & ssh below.
I am not sure if this is an "endian" issue.
Could anyone help me out in debugging this.

Thanks in advance,
Hari

======================================================server trace:

./sshd -d -d -d
debug1: Seeding random number generator
debug1: sshd version OpenSSH_2.9p2
debug1: private host key: #0 type 0 RSA1
debug3: No RSA1 key file /usr/etc/ssh/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: No RSA1 key file /usr/etc/ssh/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: Server will not fork when running in debugging mode.
Connection from 192.168.0.3 port 3795
debug1: Client protocol version 2.0; client software version OpenSSH_2.9p2
debug1: match: OpenSSH_2.9p2 pat ^OpenSSH
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-1.99-OpenSSH_2.9p2
debug1: Rhosts Authentication disabled, originating port not trusted.
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug1: dh_gen_key: priv key bits set: 128/256
debug1: bits set: 1013/2049
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug1: bits set: 1035/2049
debug2: ssh_rsa_sign: done
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
cce2 ef49 0301 2989 12ca ba7f ccf1 72e8

Disconnecting: Bad packet length -857542839.
debug1: Calling cleanup 0x2000d39c(0x0)

===========================================
client trace:

ssh -v -v -v -2 root at 192.168.0.27
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090581f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Seeding random number generator
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 516 geteuid 0 anon 1
debug1: Connecting to 192.168.0.27 [192.168.0.27] port 22.
debug1: temporarily_use_uid: 516/106 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 516/106 (e=0)
debug1: restore_uid
debug1: Connection established.
debug1: read PEM private key done: type DSA
debug1: read PEM private key done: type RSA
debug3: No RSA1 key file /home/hari/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found
debug1: identity file /home/hari/.ssh/id_rsa type 1
debug3: No RSA1 key file /home/hari/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found
debug1: identity file /home/hari/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9p2
debug1: match: OpenSSH_2.9p2 pat ^OpenSSH
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_2.9p2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit: none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r
ijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hm
ac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 124/256
debug1: bits set: 1035/2049
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /home/hari/.ssh/known_hosts2
debug3: check_host_in_hostfile: match line 12
debug1: Host '192.168.0.27' is known and matches the RSA host key.
debug1: Found key in /home/hari/.ssh/known_hosts2:12
debug1: bits set: 1013/2049
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
36a6 9c0c d787 4182 fc82 114e 8d37 0d3b

Disconnecting: Bad packet length 916888588.
debug1: Calling cleanup 0x8063510(0x0)

======================================================

Jason McCormick

2003-Aug-26 02:16 UTC

head link

Bad packet length error

> I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am
> connecting from a ssh client (openssh-2.9p2) on an x86 Linux box.
Please try upgrading to a current version.  The current version is 
OpenSSH 3.6p1.  Many bugs of this sort have been fixed long ago.

-- 
Jason McCormick
jason at devrandom.org
GPG Key: http://www.devrandom.org/gpgkey.php
GPG Fingerprint: 66C5 2B15 3E34 2B5E 5321 6147 303A DCE6 0A74 A19C

YOSHIFUJI Hideaki / 吉藤英明

2003-Aug-26 02:25 UTC

head link

Bad packet length error

In article <200308252216.39405.jason at devrandom.org> (at Mon, 25 Aug
2003 22:16:39 -0400), Jason McCormick <jason at devrandom.org> says:
> > I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am
> > connecting from a ssh client (openssh-2.9p2) on an x86 Linux box.
> 
> Please try upgrading to a current version.  The current version is 
> OpenSSH 3.6p1.  Many bugs of this sort have been fixed long ago.
3.6.1p2

-- 
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji at linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF  80D8 4807 F894 E062 0EEA

Jason McCormick

2003-Aug-26 02:27 UTC

head link

Bad packet length error

Actually meant that to be 3.6.1p2.....
-- 
Jason McCormick
jason at devrandom.org
GPG Key: http://www.devrandom.org/gpgkey.php
GPG Fingerprint: 66C5 2B15 3E34 2B5E 5321 6147 303A DCE6 0A74 A19C

Darren Tucker

2003-Aug-26 02:33 UTC

head link

Bad packet length error

"Hari (E-mail)" wrote:> I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am
> connecting from a ssh client (openssh-2.9p2) on an x86 Linux box.
> This works fine for ssh protocol version 1, but am getting the below error
> for ssh v2:
> 
> Disconnecting: Bad packet length -857542839.
There has been a history of "bad packet length" errors that were fixed
by
upgrading the version of zlib used.  What version are you using, and does
the problem go away if you recompile openssh with zlib 1.4?

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Hari

2003-Aug-26 03:32 UTC

head link

Bad packet length error

Thanks Pete,
I just tried with WORDS_BIGENDIAN defined and it helped solve this issue.
Apparently this is what happened:
I am using a cross-compiler for building openssh and I could not run
configure on the cross-compiler environment. I have initially run the
configure on an x86 box and used the thus created config.h and Makefile for
building in the cross-compiler env. At some point when I moved to power-pc,
I failed to modify/obtain new config.h and Makefile.

How do we handle this for different platforms when using a cross-compiler ?
Right now, I am doing an #ifdef _<PLATFORM>_ in config.h

Thanks,
Hari

-----Original Message-----
From: Pete Flugstad [mailto:pete.flugstad at icon-labs.com]
Sent: Monday, August 25, 2003 10:29 PM
To: hari at isofttech.com
Subject: Re: Bad packet length error


I've seen this before, and at that time, it was an
endian problem.

In OpenSSH 2.9, the aes/rijndael code needed an extra #define for
little vs big endian, WORDS_BIGENDIAN.  Obviously this needs to be
set on a big endian system and not set on little endian.   Default
is to NOT set it (i.e. default is for little endian systems).

The configure script normally figures this out, but it might
have failed on your target system.   Try setting this or
unsetting it, then rebuilding rijndael.o.

No guarantee this is correct (:-) but I hope this helps,

Pete Flugstad
Icon Labs

Steve VanDevender

2003-Aug-26 05:07 UTC

head link

Bad packet length error

Darren Tucker writes:
 > "Hari (E-mail)" wrote:
 > > I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am
 > > connecting from a ssh client (openssh-2.9p2) on an x86 Linux box.
 > > This works fine for ssh protocol version 1, but am getting the below
error
 > > for ssh v2:
 > > 
 > > Disconnecting: Bad packet length -857542839.
 > 
 > There has been a history of "bad packet length" errors that were
fixed by
 > upgrading the version of zlib used.  What version are you using, and does
 > the problem go away if you recompile openssh with zlib 1.4?

Version number confusion seems to be the order of the day.

The most recent version of zlib is 1.1.4, which also fixes some
security issues in 1.1.3.

Possibly Parallel Threads

Search for more maybe matching threads

openssh unix dev - Aug 2003 - Bad packet length error

Bad packet length error

Bad packet length error

Bad packet length error

Bad packet length error

Bad packet length error

Bad packet length error

Bad packet length error

Possibly Parallel Threads