Linked by Thom Holwerda on Wed 29th Aug 2007 00:20 UTC, submitted by anonymous
GNU, GPL, Open Source "This guest whitepaper explains how a hypervisor can be used to leverage GPL software while isolating it from proprietary code, in order to ensure compliance with the requirements of the GPL. It was written by a TRANGO Virtual Processors product manager, and uses that company's hypervisor as an example."
Permalink for comment 266530
To read all comments associated with this story, please click here.
moltonel
Member since:
2006-02-24

The (hard to get to) core idea of the article is that if you have proprietary code that must be "trusted" (as in TCPA & DRM), cou can put it in a VM instead of in the OS (as long as the OS itself is in a VM, at the same level as the proprietary code).

You would then talk to that "secure" component as if it was a server on another machine. While keeping exercising your freedom on the non-encumbered VM. Sounds like a lesser evil for tivo owners.

It's probably not usable for DRM schemes though, since you'll need to send the content to the free (non-trusted) OS at some stage.

To counter this, you can put more and more functionality into the proprietary part, but you slowly lose the advantage of beeing able to "leech" on free software. Sounds fair to me (not that I would buy such a system !). Well done, GPLv3 ;)

Reply Score: 1