In recent months I have been working with Qubes OS, a platform centered around isolating a user's workflow into different "containers" – in this case Xen virtual machines. The goal of this project is not to prevent application level exploits from taking place, or even to slow down exploitation of applications with weak security, but rather to contain a single compromised workflow from compromising other unrelated tasks the user was performing.
This weekend (March 23rd and 24th, 2013) I had was part of the red team in the Pacific Rim Collegiate Cyber Defense Competition (PRCCDC). I was given very short notice (the night before) on what my role would be in the competition, so my preparation time was close to zero. Despite not having adequate time to think about a strategy ahead of time, I figured I'd put together a summary.
Shortly after my last blog post about KDE4 and muliple monitors, a new version of kscreen was pushed into the Fedora 18 stable repository. The new version of kscreen has proven very stable and has reduced the amount of time I spent setting up monitors to nearly zero.
To install kscreen in Fedora 18 (this will pull in a few dependencies, such as kscreen)
# yum install kscreen
Qubes OS is an spin of Fedora with hypervisor level security. While Qubes OS works fine in VMWare Workstation (as it is capable of passing through VT-x, or AMD-V), the Qubes OS installer does not work properly in VMWare due to driver limitations. The installer should work via Kickstart (as described in my last blog post). But since I had already gone through the trouble of getting it working in VMWare by installing it on another machine and copying the disk into a VMDK, I decided to upload it.
Fedora 18's installer (Anaconda), lacks some functionality that previous versions of Fedora had. While other parts of the installation have become easier, partitioning drives has become more difficult.
To perform setup your drives in a more complex configuration than the GUI provides options for, youh have to create a kickstart file. Pay attention to the disk directives - the rest will vary based on your particular setup. You can use system-config-kickstart to play around with different options, if needed.