On Thu, Nov 01, 2012 at 01:50:08PM -0400, Eric Paris wrote: [..] > I've talked with and > worked with a public cloud operator who wants to prevent even a > malicious root user from being able to run code in ring 0 inside their > VM. The hope in that case was that in doing so they can indirectly > shrink the attack surface between virtual machine and hypervisor. > They hoped to limit the ways the guest could interact to only those > methods the linux kernel implemented. > > They want to launch a vm running a kernel they chose and make sure > root inside the vm could not run some other kernel or run arbitrary > code in kernel space. It's wasn't something they solved completely. > If it was, all of this secure boot work would be finished. Which is > why we are having these discussions to understand all of the way that > you an Alan seem to have to get around the secure boot restrictions. > And look for solutions to retain functionality which meeting the > security goal of 'prevent uid=0 to ring 0 privilege escalation. So will secure boot help with above use case you mentioned? I think until and unless you lock down user space too on host, it will not be possible. On the flip side, one might be able to launch windows in qemu (compromised noe) and might fool user into thinking it is booted natively and steal login credentials and other stuff. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
