Remote Access

Inspired by a pretty good write up by Cynofield as to his setup for getting a Raspberry Pi to “phone home”, I thought I’d set out how I do it. I have a machine that lives behind a ‘security’ infrastructure that makes my life a living hell. As a result, I set up automatic persistent reverse shells going back to other machines I use, so if I connect to those machines, I can get into the secure environment, without anything nasty being able to get in with me. ...

Ubuntu is one of those polarising technologies; Its really easy to use on a recreational basis, or as part of a institution/business wide rollout, but heartbreakingly awkward to use ‘alone’ within an entrenched business setting. One such setting is that of Queen’s University; the only form of secure remote access that is made (quietly) availiable is through a Citrix XenApp gateway. Great in theory; everyone can take a slice of a virtualized desktop, do whatever they need to do, and that processing power and memory can be easially reappropriated when they’re done. Unfortunately, in an effort to be ‘secure’, you HAVE to use Windows, and you HAVE to have Internet Explorer installed, and you HAVE to install the propitiatory XenApp client. ...

So, gonna do a quick write up on my current setup. Ok, from the top: Linksys WRT54GL DD-WRT v24 std firmware (also running on the bottom right screen) Generic Wireless headphones (not used since i heard someone else on the channel :P ) top screens : Windows server 2008 AMD Athlon X2 64 6000+ on an Nvidia MCP 65 based motherboard carrying 6GB, with the dangerous RAID 0 arrangement of two 500GB sata drives and an IDE 320GB for essential backups. (this system is hidden, lol) ...