Please add compression support

[GoogleCodeExporter]

ConnectBot supports zlib compression for SSH by setting a simple flag. Please 
include it to your SSHTunnel application. This will allow users to have a 
compressed SSH tunnel with another PC and potentially save cell network data 
usage.

SSHTunnel combines two very useful products in one app; ConnectBot and 
redsocks, plus it adds friendliness of an auto-reconnect. This powerful app 
allows someone to set up a transparent SSH tunnel with another PC connected to 
the internet, redirecting all internet traffic in a compressed tunnel.

Original issue reported on code.google.com by Turbo...@gmail.com on 18 Jan 2012 at 5:09

[GoogleCodeExporter]

Try BETA version instead, it just enable compression by default.

Furthermore, the java implementation (stable version) would face many problems 
when enabling the compression option. You can do some experiments with 
ConnectBot and its compression enabled by playing a youtube video.

Original comment by max.c...@gmail.com on 18 Jan 2012 at 5:40

[GoogleCodeExporter]

I tried the BETA version and it has problems as well. The "OpenSSH" client 
included in the app is not stable. My SSH server reports corrupted packets not 
long after I start using the tunnel. Even with removing the compression or 
changing the cipher in ssh.sh did not fix the problem. My server is 
Cygwin-OpenSSH, I also tried winsshd, but gives the same result, while the 
Non-beta version works perfetly with my server.

I think the compression should be available as a checkbox so that the user may 
unselect it if it doesn't work.

Also, there is no information about where your OpenSSH client included in your 
BETA version comes from. The client is located at 
/data/data/org.sshtunnel.beta/sshtunnel, and it seems to be a rename from an 
ssh client. No source code or reference.

Original comment by Turbo...@gmail.com on 18 Jan 2012 at 6:13

[GoogleCodeExporter]

You can check out openssh related source codes from here 

https://github.com/madeye/external_sshtunnel

Original comment by max.c...@gmail.com on 18 Jan 2012 at 6:17

[GoogleCodeExporter]

Thanks, do you think updating sshtunnel to the latest source code would work?
Also, in previous beta versions, you were using openssh1 and openssh2. Where 
was it from?

Thanks for the useful info.

Original comment by Turbo...@gmail.com on 18 Jan 2012 at 6:23

[GoogleCodeExporter]

Thanks, do you think updating sshtunnel to the latest source code would work?
Also, in previous beta versions, you were using openssh1 and openssh2. Where 
was it from?

Thanks for the useful info.

Original comment by Turbo...@gmail.com on 18 Jan 2012 at 6:23

[GoogleCodeExporter]

They are from the same source codes but compiled statically in the previous 
versions.

Original comment by max.c...@gmail.com on 18 Jan 2012 at 7:09

[GoogleCodeExporter]

Hi,
I basically had too choices for fixing my issues; recompile the main code by 
adding the compression flag; or find a fix for sshtunnel in the BETA which is 
causing corrupted packets.

I finally had success by replacing sshtunnel with an openssh binary from an 
Optware distribution for Android (http://nookdevs.com/Optware_for_Android). It 
works beautifully once all the dependency libraries are added to the system and 
that an /etc/passwd file is created. I can share the binaries if you wish to 
have them.

Also I had to fix the iptables so that all the ports are forwarded to the SOCKS 
proxy, not just 80/443 like it was.

Original comment by Turbo...@gmail.com on 19 Jan 2012 at 3:29

[GoogleCodeExporter]

Hi,
I basically had too choices for fixing my issues; recompile the main code by 
adding the compression flag; or find a fix for sshtunnel in the BETA which is 
causing corrupted packets.

I finally had success by replacing sshtunnel with an openssh binary from an 
Optware distribution for Android (http://nookdevs.com/Optware_for_Android). It 
works beautifully once all the dependency libraries are added to the system and 
that an /etc/passwd file is created. No more corrupted packets in the SSH 
tunnel. I can share the binaries if you wish to have them.

Also I had to fix the iptables so that all the ports are forwarded to the SOCKS 
proxy, not just 80/443 like it was.

Original comment by Turbo...@gmail.com on 19 Jan 2012 at 3:30