Hacker News Reader

You can write completely secure code and run it in a locked down VM and it won't protect you from lethal trifecta attacks - these attacks work against systems with no bugs, that's the nature of the attack.

View on HN

Sure, but if you set yourself up so a locked down VM has access to all three legs - that is going against the intention of Qubes. Qubes ideal is to have isolated VMs per "purpose" (defined by whatever granularity you require): one for nothing but banking, one just for email client, another for general web browsing, one for a password vault, etc. The more exposure to untrusted content (eg web browsing) the more locked down and limited data access it should have. Most Qubes/applications should not have any access to your private files so they have nothing to leak.

Then again, all theoretical on my part. I keep messing around with Qubes, but not enough to make it my daily driver.

If you give an agent access to any of those components without thinking about it you are going to get hacked.

If the VM has:

-Access to your private data

-Exposure to untrusted content

-The ability to externally communicate

Then it's not "locked down"

Depending on your security requirements you should have only one or two of those capabilities per VM

Reply on news.ycombinator.com