The sys admin's daily grind — Corkscrew
Sys admin columnist Charly never takes a vacation from the Internet. A beach bar with WiFi is quickly found, but it runs a forced proxy, which thinks that the SSH port (22) is in league with the devil and blocks the connection. Time to drill a tunnel.
The right tool for tunneling SSH through a proxy like Squid, Gauntlet, CacheFlow, Junkbuster, or Apache mod_proxy is Corkscrew. Why? Because the name corkscrew is well chosen, and because the program author introduces himself like this: "My name is Pat Padgett. I'm a dork." In my experience, such laconic people are great programmers.
Most distros have a Corkscrew in a back drawer somewhere; if not, you can pick it up online . The SSH daemon should be running on port 443 on the target server, because many proxies refuse to connect to port 22. Incidentally, binding the SSH daemon to two or more ports simultaneously is not a problem. To do this, you just add another port line to your
[...] Port 22 Port 443
If you are already running HTTPS on port 443, you can set up SSLH  on your server as a last resort. This is an SSH/SSL multiplexer that makes it possible to operate SSH and HTTPS simultaneously on port 443.
If the proxy asks for login credentials, you need to store them in a file. Its name does not matter; I would use, say,
/home/charly/.proxy-auth. Then, you can populate the file with data as follows:
Now you have to talk your SSH client into using Corkscrew. Edit the
.ssh/config file in your home directory for this. (If it does not exist, simply create it.) You will be adding two lines:
Host * ProxyCommand corkscrew <myproxy.example.net> <3128>%h %p /home/<charly>/.proxy-auth
Of course, you need to change
<myproxy.example.net> and the port number to suit your local situation. The variables
%p pass the parameters from the SSH call to Corkscrew. If you use a server without authentication, you just leave out the path to the username/password file.
Now, it's time for the premiere. The target server I use is a Raspberry Pi, whose
sshd listens on port 443. The proxy is a standard Squid. As you can see from Figure 1, the login works fine – there is nothing to suggest that Corkscrew has a hand in the game, unless someone has access to the proxy logs. You would find the following entry, if you looked:
"CONNECT 10.0.0.5:443 HTTP/1.0" 200 <[...]>
But, who cares about logs while you're relaxing in a beach bar? Ah, they have WiFi.
Charly Kühnast is a Unix operating system administrator at the Data Center in Moers, Germany. His tasks include firewall and DMZ security and availability. He divides his leisure time into hot, wet, and eastern sectors, where he enjoys cooking, freshwater aquariums, and learning Japanese, respectively.
- Corkscrew: http://www.agroman.net/corkscrew/
- "The sys admin's daily grind: sslh" by Charly Kühnast, Linux Magazine, Issue 111, 2010: http://www.linux-magazine.com/Issues/2010/111/Charly-s-Column/(language)/eng-US
Buy this article as PDF
The bug was introduced back in 2009 and has been lurking around all this time.
The new release deprecates the sshd_config UsePrivilegeSeparation option.
Lives on as a community project
Five new systems join Dell XPS 13 Developer Edition that come with Ubuntu pre-installed.
The Skype Linux client now has almost the same capabilities that it enjoys on other platforms.
At CeBIT 2017, OpenStack Day will offer a wide range of lectures and discussions.
A major setback for the Linux desktop.
Improved support for GPU in virtualization.
News site for the openSUSE community falls victim to a Wordpress exploit.
The source code is available online.