neophob.com

If you want to cre­ate SSH tun­nels its a bit annoy­ing when your SSH ses­sion dis­con­nects. There are some tools avail­able which pre­vents that:
–Call­ing Home
–MyEn­tun­nel

Call­ing Home didn’t work for me; I assume this is because of a newer MS .NET frame­work. What you need for both tools is an auto­matic SSH logon. I cre­ated a SSH DSA Key pair for my client.

You need putty and pgen. SSH­Server is the machine you want to con­nect to, WORK is the machine you are con­nect­ing from.

–WORK: start put­ty­gen, gen­er­ate a ssh-2 DSA key (1024bits)
–WORK: copy the “Pub­lic key for past­ing…“
–SSH­Server: paste it to the file ~/.ssh/authorized_keys. (bad exam­ple: if you want to con­nect as root, copy the pub key file to /root/.ssh/authorized_keys)–WORK: save the pri­vate key on your win­dows machine (in this exam­ple c:priv.ppk)
–WORK: when you con­nect to the Linux server with putty, use c:priv.ppk as “pri­vate key file for authen­ti­ca­tion” (Connection/SSH/Auth)

If you remark some issues when you are con­nect­ing with the DSA key, try to delete the file ~/.ssh/known_hosts on your SSHServer.

Now start putty and load your saved ses­sion. Edit the host name, add a USERNAME@ in front of your host. For exam­ple if your
host name is 192.168.10.10 edit it to root@192.168.10.10. Save the ses­sion and try if it works.

As i cant use Call­ing Home is use MyEn­tun­nel as an exam­ple. MyEn­tun­nel use plink as SSH back­end. Plink pro­vides those options:

The impor­tant part is “host” can also be a PuTTY saved ses­sion name. Because you can’t enter proxy set­tings (and the other putty options)
we need to enter the putty ses­sion name, user­name and the SSH port:

Now MyEn­tun­nel (plink) will use our saved putty ses­sion PUTTY-TEST (and thus can use a proxy server), con­nect to port 443 as root.