Miloslav TrmaÄ <mitr <at> volny.cz> writes:
> On Thu, Jun 23, 2011 at 4:21 PM, JB <jb.1234abcd <at> gmail.com> wrote:
> > Will the TPM allow a third party remote access to the machine ?
> Absolutely not.
You are wrong here.
... It also includes capabilities such as remote attestation ..."
So how do we ensure that software is not leveraging this by default and is
> > By the virtue of beeing associated with the "root of trust" ?
> "Root of trust" in TPM lingo is something different - it's "we
> that the kernel and related software we run has not been tampered
> with". The root of trust is established by the tboot blob, which
> should verify the state of all relevant hardware.
There is more to that.
With regard to "root of trust" origin, meaning, applications:
1. OS privilege isolation
Who remembers the ring hierarchy introduced on the 286 that allowed
creating an operating system with privilege isolation?
Trusted Execution Technology (TXT) comes as a reinforcement to deal
threats that act on the same level of the kernel operating system or
more privileged levels -- like hypervisorâs malware, where the
code can take advantage of the CPU virtualization instructions to
hardware instructions and completely control the operating system.
2. platform integrity (hardware plus software)
... In this context "integrity" means "behave as intended" and
a "platform" is generically any computer platform - not limited to PCs
just Windows ...
Together with the BIOS, the TPM forms a Root of Trust: ...
3. DRM; Software Licensing.
Other uses and concerns
Almost any encryption-enabled application can in theory make use of a
Digital rights management
Software license protection & enforcement
devel mailing list
in your fear, seek only peace
in your fear, seek only love