“Don’t tell anyone that I’m free”
WinSSH
Update (10/July/2016): OpenSSH (7.2p2) Server for Windows (7.2p2 is latest version of OpenSSH)
OpenSSH (6.4p1) Server for Windows (Previous version of OpenSSH)
General Features:-
* Security, if you want to access your Windows Machines cmd shell with full security.
* Windows NT Service Support
* Full install about 12mb, installer under 8mb (Including Cygwin dependencies)
* Windows Command Prompt support for SSH Terminal
* SCP/SFTP server support (secure file transfer)
* Command-line clients included Read the rest of this entry »
Using ssh as a proxy or encrypted tunnel to browse the web can sometimes be necessary:
- When you’re at some public place but need to login securely to your work place.
- When local access restrictions make life really difficult.
I use SSH for the security reasons. I want to make sure that my security and login information will remain secure:
ssh -D 12345 myuser@remote_ssh_server
Replace myuser with your user account and remote_ssh_server with the IP or Hostname of your server.
The above command will do all, but if you want to add more options, you can add other options like:-
-D 12345: This does the dynamic stuff and makes it behave as a SOCKS server.
-f : This will fork the process into the background after you type your password (for Linux only, on windows skip that).
-C : Turns on compression.
-q : Quiet mode. Since this is just a tunnel we can make it quiet (for Linux only, on windows skip that).
-N : Tells it no commands will be sent. (the -f will complain if we don’t specify this)
Next, set up your browser to use the proxy server. Most browsers include proxy support. For Firefox, go to Edit→Preferences→Advanced→Network→Settings, and specify that you want to use a Manual Proxy, localhost, port 12345 and SOCKS v5 (although OpenSSH supports both versions 4 and 5).
HTTP Proxy (The first input). Must be left blank and add this config to SOCKS only.
Now your browser is using a secure tunnel to your remote SSH server, Enjoy
In previous versions of PuTTY, 0.59, 0.60 and 0.61, the password used to log on to an SSH2 server was retained in memory.
The password was then retrievable by other programs that could read the memory, or could be found in swap files and crash dumps.
The update also fixes non-security-related errors including correcting the rendering of underlines and VT100 line-drawing characters, removing a spurious GSSAPI authentication message, restoring saved sessions, and closing a leak of file mapping handles when authentication failed.
Details of the changes are in the release notes. Pre-built binaries and source code for the MIT-licensed PuTTY are available to download.
