<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Bruno Schaatsbergen</title><link>https://bschaatsbergen.com/posts/</link><description>Recent content in Posts on Bruno Schaatsbergen</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bschaatsbergen.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>A TPM has a clock, but it does not have the time</title><link>https://bschaatsbergen.com/posts/tpm-clock/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate><guid>https://bschaatsbergen.com/posts/tpm-clock/</guid><description>&lt;p&gt;I have a confidential VM running for some attestation work. It has a virtual
TPM, which reports its manufacturer as &lt;code&gt;GOOG&lt;/code&gt;. I was poking at it and ran
&lt;code&gt;tpm2_readclock&lt;/code&gt;, expecting a timestamp somewhere in there.&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;$ sudo tpm2_readclock
time: 964062646
clock_info:
 clock: 964065681
 reset_count: 15
 restart_count: 0
 safe: yes
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;No date. I went looking for why, assuming I&amp;rsquo;d missed a command.&lt;/p&gt;
&lt;h2 id="what-a-tpm-is"&gt;what a TPM is&lt;/h2&gt;
&lt;p&gt;A &lt;a href="https://trustedcomputinggroup.org/resource/tpm-library-specification/"&gt;TPM&lt;/a&gt;
is a small, slow processor that holds keys and won&amp;rsquo;t give them back. You can
ask it to sign something. You can&amp;rsquo;t ask it for the key.&lt;/p&gt;</description></item></channel></rss>