I know it’s been a while since my last post.
There is lots to talk about, but let’s start afresh with something short and sweet.
Let me paint a picture for you:
There is something broken in the most holy and secure part of your network. You need to call support to have them look at it. The support rep wants console access, but you can’t give them axx to your holiest cream pie.
They offer to take over your desktop with a java rootkit app like TeamViewer, GoToMeeting or WebEx.
You decline. You need to stay in control, but show them what they need to see, that and only that.
Let me be clear on the problem statement:
Read-only shell access to the most secure host, which is not available over the wire, viewed by multiple parties at the same time.
Here’s how to do that with SSH, screen(1) and some foo,
with ssh->chroot->rbash->readonly multiuser screen->reverse ssh->openvpn:
You will need a linux server in an “unsafe” zone which is exposed to your support rep on the internet or thru VPN.
- Create the user to be contained on your unsafe box, with the restricted bash shell:
unsafe# export user=rep; adduser $user; chage -s /usr/bin/rbash $user
- (Bonus:) chroot/contain the user within sshd_config
- Setup multiuser screen on the unsafe box. There are lots of guides for it, but the short and sweet of it is:
unsafe# chmod +s `which screen`; chmod 755 /var/run/screenIndeed, this increases the attack surface, and therefore we call this box the unsafe one.
- ssh from secure zone to unsafe server:
secure# ssh -R 2222:localhost:22 screen
- Run screen from YOUR account and do
:addacl $user :chacl $user -w "#" :chacl $user -x "?"Replace
$userwith whatever from step 1. Then, still in your screen:
- Win! Now you can reverse ssh back to the secure zone and let $user on the unsafe box read the terminal without being able to access anything but what you show her.
- Bonus: Add
`screen -r $youraccount`in
$user/.profileand $user will drop straight into locked screen, and remember that multiuser screen is read-write-execute for all accounts that are addacl’d
so you might want to chacl before enabling the $user account login.
And there you have it, superparanoid reverese secure-unsecure remote shell viewer.