http://news.ycombinator.com/item?id=1246990
http://news.ycombinator.com/item?id=2645170
This story won't see much traction on HN. The cult of Mac is too strong, and HN users generally aren't interested in secure operating systems.
As far as I remember you could use different kernels for Xen VMs and the physical hardware, then the only way to compromise the system would be if I could escalate privileges on the hypervisor, right?
Now you can read up on Mark Miller's published papers [2] on Joule (actually pretty secure) and some of the issues associated with making things secure and get a much better feeling of solidity (for example).
So when the press release comes out that its passed the Defense department's B1/B2 review, then I suspect it will get a lot of interest here and else where.
[1] http://www.linkedin.com/profile/view?id=10279027 LinkedIn profile, one job CEO of this thing? A blog full of black hat sort of exploits but I didn't see any peer reviewed work.
[2] http://research.google.com/pubs/author35958.html
[3] http://en.wikipedia.org/wiki/Trusted_Computer_System_Evaluat...
The "black hat sorts of exploits" attributed to her tend to be things like, "abusing odd, barely-documented corners of x86 chipsets to bypass hardware-encrypted trusted boot roots". Thinking less of a professional in my field for having exploits attributed to them tends to be a bad idea, but it's a uniquely bad idea in Rutkowska's case.
Outside of conference presentations, Rutkowska doesn't have much peer-reviewed work in the literature. That's because Rutkowska is originally from the malware/rootkit/virus part of the industry. For obvious reasons, antivirus doesn't generate a lot of peer-reviewed academic research. One of those obvious reasons is that they're too busy printing money hats to bother. (This to my chagrin; I am very much not from the AV/malware part of the field).
I'm not vouching for Qubes or even saying that I think the approach (of semi-transparently allocating secure VMs for each application or trust domain on the system) is viable. But Rutkowska is worth taking seriously.
SKPP pretty much sucked off all the "paper-writing industry" folks a few years ago into a kind of boring niche. Mark Miller is a big exception to that, but it's not a really vibrant research area compared to other parts of security now.
There's a continuum of security and usability between having (a) N machines in N rooms for N tasks to having (b) 1 machine on a single desk running N tasks. You can have a KVM switch and multiple computers sharing a keyboard/mouse/monitor, which gives you a high degree of isolation (very close to (a)), or you can have compartment mode, where windows themselves have security labels, but then you need an advanced system to protect apps in one window from other windows, including window masquerading attacks. If you do it well, it's ideally close to (a) as well.
The problem with virtualization on a desktop is that certain resources (video/keyboard drivers) don't like to be virtualized, so you end up running them in the system host area. Applications also tend to want pretty low-level access to those resources. It used to be the performance overhead of all of this was very high, but now it's not as big a deal (at least for normal 2d type apps).
The last good Compartment Mode Workstation I remember was Trusted A/UX (built on apple's first UNIX operating system) from the early 1990s. It wasn't particularly good.
Almost on topic: I have to say the team is also really cool and approachable at conferences - and for that I'm very grateful as a member of the unexperienced audience. They can really adjust the explanations to the right level for the general crowd, which must be quite hard considering the topic.
Touch-based (and by extension, NUI-based) OS'es and mobile applications are the future. Windows always sucked. Mac OS always sucked. Every desktop OS ever built sucked because it is a horrible way to use a computer. Nobody ever really wanted to use these terrible desktop metaphor systems... they only ever did because they had to.
Security has a vital place in every OS, regardless of the skin you put over the top of it.
I guess the desktop environment was just a random choice of "this works, so just leave it in" from whatever distribution they started with.
Granted, browsers aren't without their security holes, but then again, neither are operating systems. Given the amount of effort being put into browsers to make them secure (especially Chrome), my money's on that.
The meta issue here is that clearly the black hat work has some 'trade secret'ness too it in terms of competitors but it cries out for being published/peer reviewed post-money making opportunity or something.
>(...) But then again, I'm biased, of course ;)
At least, they are honest heh
Touch screens are to desktops as push bikes are to tractors. You need both. Some people even use both. Or just one. Or neither.
Maybe you feel this way because you've been driving a tractor around all this time and you feel like you've been wasting your time, however some of us (I imagine a lot of us on HN) like to do farming occasionally :-)
"If I had asked people what they wanted, they would have said faster horses."
People do not desire better desktop operating systems. They want computers to disappear. It simply does not matter how good this awesome new, secure, desktop OS is because it's built for a world that doesn't exist anymore.http://blogs.hbr.org/cs/2011/08/henry_ford_never_said_the_fa...
However, we still use horses as transport. Sure, it's often just for pleasure, but the Police still use them, and rural people still use them, or people in mountains etc, because in those situations they are still better than anything Ford came up with.
So I don't think that quote is relevant here. People have accepted 'post-pcs' into their lives and they are good at lots of things. There are things that larger 'real' computers are better at though, and I don't see any evidence that will change.
To be fair, Apple's focus on usability and convenience could be linked to Qubes, in that they represent very different points on the "How much users should be thinking about security" spectrum.
It makes me long for the day that current pc's end up relegated to the attic of computing.
The extra requirements for this seem to be (ignoring that this isn't yet released) that you're having vt-x support, for all I remember.
This system goes at least 2 layers deeper. System itself makes sure that each window has its own desktop environment and can't see others. Hardware takes care about the separation between security containers the apps are running in. Protection of the app itself is just the first line of defence and is not going away, so whatever sandboxing exists in the browser still applies.
They are also talking about protecting hardware sharing from being used to cross boundaries which is another layer of paranoia (not unwarranted)
You say that nobody wants to use desktops and people want computers to disappear. Unlike you, I don't believe that already, so do you have some evidence for it?
If you build a webmail client, you need to know all about these attack vectors, and you need to go out of your way to prevent your application from being susceptible to them. Websites are insecure by default.
I don't trust a web browser with my email at all. Not yet. If I were to use webmail, I'd make sure to set up a separate instance of Firefox to run it in, with it's own profile. I will continue to use Thunderbird for now though.
I'm not against the idea of using webmail, I just don't think the web is secure enough yet.
I think MAC (Mandatory Access Control) applied to a desktop environment, picking a better language than C and actually thinking about stuff is more than sufficient to get around the existing problems...
Virtualization is just another pile of complexity and performance problems to deal with. It's not a magic bullet. Consider the following as well:
http://www.c0t0d0s0.org/archives/3651-Theo-de-Raadt-about-vi...
I really don't want this solution.
I'm sick of the lack of control over my data I have on android (not to mention iOS).
Nice video here: http://www.youtube.com/watch?v=pzviQLCPCG4
An application can read the unique ID of the device (which is used for session persistence between service calls) but not access any other information unless allowed to.
Effectively there is no way for it to steal all the data in that list unless you physically tell it that it's ok to do it.
It's the mobile platform that scares the shit out of me the least. They did good here.
Took my old brain a second or two to realize that I had previously heard that quote associated with Henry Ford.
LUKS is used for all filesystems. Qubes was specifically engineered to block the Evil Maid scenario and similar vectors for notebooks. See pg. 31 from http://qubes-os.org/files/doc/arch-spec-0.3.pdf:
"There are several things that all together make the storage secure in the Qubes architecture:
1. Confidentiality, understood as preventing one VM from reading other VMs data
2. Confidentiality, understood as preventing access to the data when the machine is left unattended (full disk encryption, resistance to Evil Maid attacks, etc)
3. Integrity, understood as preventing one VM from interfering with the filesystem used by other VMs
4. Security non-critical role: a potential compromise of the storage subsystem doesnʼt result in other system components, like other VMs, compromise. Storage subsystem is not part of the TCB in Qubes OS."
See also, Section 7.1 System Boot Process, and 8.5 Resistance to Physical Attacks (or just search for "disk encryption").
Academic pubs != Relevance
Edit: But since you asserted it, here are researchers that cite her work (over 130, including IEEE and ACM folk):
http://scholar.google.com/scholar?cites=13610021170603453007...
They're throwing another roomful of people together to build something similar right now. If Joanna wants and maneuvers right, her lab could end up getting a lot of the contracts to do a lot of things the DoD wants done.
I'm not sure whether she's interested in that though, or whether she's pursued it already. They'd probably ask for a bunch of stuff that would involve headaches. Either that or she's already doing work on it. Dunno, to be honest.