Please do share how can one escape qemu.

At your service:

https://www.techrepublic.com/article/vm-escape-flaw-in-qemu-...

Beautiful! Thank you.

> I did not see any relevant content on the websites you mention in your HN profile

At least I have a filled out profile, unlike you.

Besides that, and the cheap personal attacks, you seem to be completely missing the point so let me spell it out for you: VMs, containers, chroot jails and all those other tools with which we can try to isolate two pieces of software running on the same hardware all have exploits, past, current and future ones. Any piece of software of even moderate complexity will have bugs, any isolation method should be considered fallible and leaky and you best defenses will take that into consideration when architecting your setup.

If you don't then sooner or later someone with more patience, a larger budget or more knowledge than you will get the better of you with all the consequences that may have.

The idea is that virtualization escape vulnerabilities are quite frequent. An attacker might not have one on hand at any given moment and you might patch your system frequently when they become known.

But this only means a determinated attacker that has emulated root needs only patience. Good security always means stacked independent layers, betting the farm only on the guarantees of your VM is very unsafe.

I'm trying to understand what your point is, are you denying that there was a vulnerability?

As it stands it just sounds like you are just being a jerk on the internet.

I am asking for actual code that shows his statement is still true.

The statements I read as an answer to my question contain zero value and still lots of very unrelated words.

If you are sure there are vulns right now, please publish them. If not, shut up.

Nillywilly "computers might be insecure" is on a level I would not expect to read on a side like this one.

I just want to keep the quality level high for this news discussion site.

Can you please stop posting like this to HN? You've done this sort of haranguing a lot and it's not in the spirit of this site:

https://news.ycombinator.com/item?id=21812936

https://news.ycombinator.com/item?id=21812863

https://news.ycombinator.com/item?id=21812806

https://news.ycombinator.com/item?id=21656610

https://news.ycombinator.com/item?id=21656527

Please review the guidelines: https://news.ycombinator.com/newsguidelines.html. Note that they include: "Have curious conversation; don't cross-examine."

Running in a VM is good. Running in a VM as a non-priv user is better. Ideally you'd want multiple layers of defense in case of undiscovered gaps, human error and 0-days.

Not many if its Qubes OS.

One would be quite enough.

In fact, Qubes is using hardware virtualization IOMMU/VT-d [0], which has been escaped only once in 2006 by the project founder [1].

[0] https://www.qubes-os.org/doc/architecture/

[1] https://en.wikipedia.org/wiki/Blue_Pill_(software)

I trust Joanna Rutkowska's competence, but I wouldn't bet too much on chip makers not messing up again in the future.

It will be progressively harder, but it will happen.