<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kop316</author><text>Hello!&lt;p&gt;I am curious about a couple of things:&lt;p&gt;Assuming you use Intel chips, how do you manage to trust the firmware&amp;#x2F;ME from them? Do you write your own BIOS to ensure that it is safe? Or do you use ARM&amp;#x2F;PowerPC&amp;#x2F;other ISA and have an entirely open source stack?&lt;p&gt;Does the Titan assume no phyiscal access? And if you do assume someone could steal the chip&amp;#x2F;try to reverse engineer the chip, do you have anything in it to stop an adversery? I would wonder if there would be a private&amp;#x2F;nation state agency would want access to certain secrets so bad that they would try to alter it physically, rather then through root access.</text><parent_chain><item><author>bluegate010</author><text>Hey HN, I&amp;#x27;m one of the engineers on the team behind Titan, feel free to AMA.</text></item></parent_chain></comment><story><title>Titan in depth: Security in plaintext</title><url>https://cloudplatform.googleblog.com/2017/08/Titan-in-depth-security-in-plaintext.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>puzzle</author><text>Does LOAS use Titan, then?&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;jbeda&amp;#x2F;status&amp;#x2F;715373975182807040&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;jbeda&amp;#x2F;status&amp;#x2F;715373975182807040&lt;/a&gt;&lt;p&gt;Will you convince Niels to publish a paper?</text><parent_chain><item><author>bluegate010</author><text>Hey HN, I&amp;#x27;m one of the engineers on the team behind Titan, feel free to AMA.</text></item></parent_chain></comment><story><title>Titan in depth: Security in plaintext</title><url>https://cloudplatform.googleblog.com/2017/08/Titan-in-depth-security-in-plaintext.html</url></story>