One promise of Trusted Computing is better protection of system integrity. Various applications can profit from mechanisms that protect software on a computer from being tampered with. To this end, a v1.2 TPM supports authenticated boot, keeping track of the boot process and eventually basing operations such as sealing and attestation upon the result. This is one step short of what theory suggests for best security: stopping the boot process of fixing the issue as soon as a manipulation has been detected [1, 2]. This leads to the question what the implications of this difference are in practice
