<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>T-SeriesのトピックRe: T2080 Secure vs. Trusted</title>
    <link>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271610#M4057</link>
    <description>&lt;P&gt;Your understanding is correct.&lt;/P&gt;</description>
    <pubDate>Tue, 04 May 2021 08:12:57 GMT</pubDate>
    <dc:creator>ufedor</dc:creator>
    <dc:date>2021-05-04T08:12:57Z</dc:date>
    <item>
      <title>T2080 Secure vs. Trusted</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271338#M4052</link>
      <description>&lt;P&gt;The documentation describes two following security states: Trusted and Secure.&lt;/P&gt;&lt;P&gt;What is the functional difference between the two in this specific SoC, in terms of available mechanisms, violations behavior, available keys, etc.?&lt;/P&gt;&lt;P&gt;Is Secure considered to be "more secure", and if yes then in what way?&lt;/P&gt;&lt;P&gt;Are there any functionalities that are available in only one of the states?&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Dmitri&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 15:31:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271338#M4052</guid>
      <dc:creator>dmitri_lechtchinski</dc:creator>
      <dc:date>2021-05-03T15:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 Secure vs. Trusted</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271374#M4054</link>
      <description>&lt;P&gt;The modes are described in the QorIQ Trust Architecture 2.0 User Guide, 7.2.6.1.2 State definitions.&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 17:31:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271374#M4054</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2021-05-03T17:31:53Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 Secure vs. Trusted</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271601#M4055</link>
      <description>This chapter doesn't really answer these questions.. I see no major difference between the two states, can you elaborate please? Additionaly, this document states in the mentioned chapter: "In the device, there is limited difference between Trusted and Secure State. This distinction is more relevant in other NXP devices that also use the security monitor." Does this mean that specifically in T2080 there is no functional difference between the two?</description>
      <pubDate>Tue, 04 May 2021 07:52:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271601#M4055</guid>
      <dc:creator>dmitri_lechtchinski</dc:creator>
      <dc:date>2021-05-04T07:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 Secure vs. Trusted</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271610#M4057</link>
      <description>&lt;P&gt;Your understanding is correct.&lt;/P&gt;</description>
      <pubDate>Tue, 04 May 2021 08:12:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271610#M4057</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2021-05-04T08:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 Secure vs. Trusted</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271611#M4058</link>
      <description>Thanks!</description>
      <pubDate>Tue, 04 May 2021 08:17:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-Secure-vs-Trusted/m-p/1271611#M4058</guid>
      <dc:creator>dmitri_lechtchinski</dc:creator>
      <dc:date>2021-05-04T08:17:56Z</dc:date>
    </item>
  </channel>
</rss>

