Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Can not connect and receive "Incoming packet was garbled on decryption" msg.

belamy2 wrote:

I've tried to use WinSCP2 ver. 2.2.3 to connect to remote host. My problem is I can not connect to remote server and recive message: "Incoming packet was garbled on decryption".

Please read Putty FAQ on "A.6.18 Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY" (<invalid hyperlink removed by admin>). According to this document, problem is on the server side. Workaround is to use SSH2 with Blowfish encryption. Please, let me know, if it helps.
Grand Apeiron

RE: Can not connect and receive "Incoming packet was garbled on decryption" msg.

Hi all,

i just expected the same problem when connecting
to a sshd2 on a debian woody machine.
"Incoming packet was garbled on decryption"
If i use sftp2 on that debian machine to connect to itself everything works fine.

If i try psftp i get the following error:
Fatal: unable to initialise SFTP: could not connect
Verbose output is:
======

Looking up host "10.1.4.1"
Connecting to 10.1.4.1 port 22
Server version: SSH-1.99-2.0.13 (non-commercial)
We believe remote version has SSH2 HMAC bug
We believe remote version has SSH2 key-derivation bug
We claim version: SSH-2.0-PuTTY-Release-0.53b
Using SSH protocol version 2
Doing Diffie-Hellman key exchange
Host key fingerprint is:
ssh-dss 1024 5d:99:13:16:8d:3b:e7:8f:1c:52:58:60:2c:47:64:45
Connected to 10.1.4.1
Fatal: unable to initialise SFTP: could not connect

======


I have no problems to connect to debian machines which are running sshd (not sshd2).
So i would suggest its a problem with sshd2.

If you need further information just tell me.


Thanx in advance,
Grand Apeiron
belamy2

Can not connect and receive "Incoming packet was garbled on decryption" msg.

I've tried to use WinSCP2 ver. 2.2.3 to connect to remote host. My problem is I can not connect to remote server and recive message: "Incoming packet was garbled on decryption".
When I use "scp" command form linux system to connect to that remote host all files are copied correctly.

Below is debug log from my "scp" linux connection:

OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 500 geteuid 0 anon 1
debug1: Connecting to egb.pl [xxx.xxx.xxx.xx] port 22.
debug1: temporarily_use_uid: 500/501 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 500/501 (e=0)
debug1: restore_uid
debug1: Connection established.
debug1: read PEM private key done: type DSA
debug1: read PEM private key done: type RSA
debug1: identity file /home/user/.ssh/identity type -1
debug1: identity file /home/user/.ssh/id_rsa type -1
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version 2.0.13 (non-commercial)
debug1: match: 2.0.13 (non-commercial) pat 2.0.13*,2.0.14*,2.0.15*,2.0.16*,2.0.17*,2.0.18*,2.0.19*
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.1p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client 3des-cbc hmac-md5 none
debug1: kex: client->server 3des-cbc hmac-md5 none
debug1: dh_gen_key: priv key bits set: 184/384
debug1: bits set: 542/1024
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'egb.pl' is known and matches the DSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug1: bits set: 511/1024
debug1: ssh_dss_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
debug1: buggy server: service_accept w/o service
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password
debug1: next auth method to try is publickey
debug1: try privkey: /home/user/.ssh/identity
debug1: try privkey: /home/user/.ssh/id_rsa
debug1: try privkey: /home/user/.ssh/id_dsa
debug1: next auth method to try is password
user@remote.host.com's password:

and after entering password files are copied.