The sys admin's daily grind: Shell In A Box
Sea Shells in a Box
The web login tool I am looking at today is available in many distributions, or you can download it from the website . I got Shell In A Box to jump onto my Kubuntu lab machine like this:
apt-get -fym install shellinabox
It runs as a service in the background, normally listening on port 4200. When I then surf to localhost:4200, I see the Bash login prompt and can log on and go about my work in the normal way (Figure 1). It doesn't even have to be a full login. I can also redirect the output from programs running in Bash to the web.
Shell In A Box is easily configurable. Typing
shellinaboxd -t--localhost-only -p 8001--no-beep -s'/htop/:nobody:nogroup:/:htop-d 5'
beams the Htop process monitor into the web. The
-t parameter disables SSL encryption, which is enabled by default. Switching this off here is less critical than you might think, because I am only letting Shell In A Box listen locally on 127.0.0.1 – in a box in the true sense of the word. If you don't like the idea of the default port (4200), you can choose a different one; this is handled by
-p 8001 in my example. The
--no-beep option disables the annoying notification tones.
-s parameter is followed by the actual shell command, whose output you want to display in the browser. You can do this with multiple box shell instances at the same time, which is why I specified a URL (
/htop) to distinguish between the instances. To see the output, I thus need to enter a URL of http://127.0.0.1/htop in my browser's address bar. The results look like Figure 2.
Besides statically displaying the typical text flow from standard command-line tools, the browser also supports interactive working, assuming that the tools you use have an interactive mode. For example, if you press the M key in the Htop output, the browser shows the processes sorted in descending order by memory requirement, just as in the native command line.
As always in production operations, I would advise caution with the
shellinaboxd. If you export your Bash to the web, you should at least insist on HTTPS. The user rights also need to be as conservative as possible, as shown in the Htop example, where I specified
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.
- Shell In A Box: https://code.google.com/p/shellinabox/
Buy this article as PDF
Weird data transfer technique avoids all standard security measures.
FIDO alliance declares the beginning of the end for old-style login authentication.
Legendary Uber-distro splits over the systemd controversy.
One of CeBIT’s most successful forums returns in 2015.
A new study says it is possible to unmask 81% of TOR users.
Redmond joins the revolution by turning the .NET Core Runtime into a GitHub project.
Users only had 7 hours to update before the intrusions started.
It's official: The new web arrives