Connection hang on "Using algorithm: aes256-cbc hmac-sha1-96" message

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Ensure the phone is connected to 3G network
2. Launch ConnectBot
3. Connect to a ssh server using port 443 (my 3G allows only 80 and 443 ports)
4. Wait....

What is the expected output? What do you see instead?
The ssh connection should be done and we should have a prompt.
I only see 
Connection to .....:443 via ssh
Verified host 'RSA" key: .....
Using algorithm: aes256-cbc hmac-sha1-96
ConnectBot stays bloqued, no timeout error

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
ConnectBot 1.6.2(r80 2010.02.12)

What type of system are you trying to connect to?
Wireless router Linksys WRT54GL with DD-WRT 2.4.34-pre2 firmware

If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?
xterm, Linux DD-WRT 2.4.34-pre2 #169 Fri Sep 15 20:01:08 CEST 2006 mips unknown

Please provide any additional information below.
Connection via wireless network is ok
Connection via 3G is ko
Before that, connection to an Ubuntu machine in the same network was
working via 3G (443 port was redirected to this machine but it was the same
DNS address)
I may have had a message on ConnectBot when changing connection parameters
(user name is not the same on dd-wrt than on the Ubuntu machine) like when
ssh has saved know-hosts and the host you want to connect to has changed
(talking about man-in-the-middle attack). I can't see this message anymore,
I can't remember what I clicked.

Original issue reported on code.google.com by mass...@gmail.com on 4 Mar 2010 at 2:48

[GoogleCodeExporter]

I am experiencing the exact issue.

I am using connectbot version 1.6.2 (r480 2010.02.12)

I am attempting to connect to an Ubuntu 10.04 linux box, using 3G with a VPN 
using 
the built-in VPN capabilities of android 2.1, using a PPTP encryption setting.

Using ps I can see that the sshd processes are running while it hangs.
Checking auth.log shows that the password is accepted for the user, a session 
is 
opened for the user and then instantly closed for the user.

Original comment by indulge....@gmail.com on 24 May 2010 at 7:14

[GoogleCodeExporter]

Well aparently the problem was due to the use of the Compression parameter. I 
have unchecked the option and can connect now to my router.
Maybe the problem is on the router side, but I think its ssh daemon works with 
compression.

Original comment by mass...@gmail.com on 14 Sep 2010 at 6:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I think this should be fixed in 
https://github.com/kruton/connectbot/commit/6538b319af57762632aa119710f5fbe17aef
04c9

It occurs when the 'zlib' compression (OpenSSH's "compression yes" rather than 
"compression delayed") is set.

Original comment by matt.gtalkfix@gmail.com on 31 Jan 2011 at 1:01

[GoogleCodeExporter]

Not fixed as of 1.7.1

Original comment by scree...@gmail.com on 10 Sep 2011 at 7:14