<?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>topic How install data on integrity protected partitions during production using i.MX6 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/How-install-data-on-integrity-protected-partitions-during/m-p/1284123#M174676</link>
    <description>&lt;P&gt;When installing a new board support package from SD card&lt;BR /&gt;on the emmc of our board the following steps happen:&lt;BR /&gt;1. create a random key&lt;BR /&gt;2. encrypt it&lt;BR /&gt;3. store it on both the boot boot partition&lt;BR /&gt;4. decrypt the key and store it in RAM&lt;BR /&gt;5. we format the app end the home partition using the key from RAM&lt;BR /&gt;and the command "integritysetup format"&lt;BR /&gt;5. we open the app end the home partition using the key from RAM&lt;BR /&gt;and the command "integritysetup open" and copy the data from SD&lt;BR /&gt;card to eMMC&lt;BR /&gt;6. we close the app and the home partition&lt;/P&gt;&lt;P&gt;When we later boot from eMMC, the key is loaded and decrypted and the protected partitions are mounted.&lt;/P&gt;&lt;P&gt;The question is, when can we burn the fuses, in particular the "secure boot" fuse such that the unique, per device key is used for integrity protection?&lt;/P&gt;&lt;P&gt;If we do that before encrypting the key using the command "caam_tool enc", will the caam tool detect that the device is a secure device? I think it will not, because the device only becomes a secure device after power cycling.&lt;/P&gt;&lt;P&gt;So how can I create a secure device AND use per-device key for integrity protection without having to power cycle the device twice during the installation process?&lt;/P&gt;&lt;P&gt;The web page &lt;A href="https://github.com/f-secure-foundry/caam-keyblob/" target="_blank"&gt;https://github.com/f-secure-foundry/caam-keyblob/&lt;/A&gt; says:&lt;BR /&gt;"The secure operation of the CAAM and SNVS, in production deployments, should always be paired with Secure Boot activation."&lt;/P&gt;&lt;P&gt;Does this always requires an addition power cycling of the board before installing data on the secure partition?&lt;/P&gt;&lt;P&gt;Best regards:&lt;/P&gt;&lt;P&gt;Uwe Fechner&lt;/P&gt;</description>
    <pubDate>Fri, 28 May 2021 11:05:44 GMT</pubDate>
    <dc:creator>ufechner</dc:creator>
    <dc:date>2021-05-28T11:05:44Z</dc:date>
    <item>
      <title>How install data on integrity protected partitions during production using i.MX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-install-data-on-integrity-protected-partitions-during/m-p/1284123#M174676</link>
      <description>&lt;P&gt;When installing a new board support package from SD card&lt;BR /&gt;on the emmc of our board the following steps happen:&lt;BR /&gt;1. create a random key&lt;BR /&gt;2. encrypt it&lt;BR /&gt;3. store it on both the boot boot partition&lt;BR /&gt;4. decrypt the key and store it in RAM&lt;BR /&gt;5. we format the app end the home partition using the key from RAM&lt;BR /&gt;and the command "integritysetup format"&lt;BR /&gt;5. we open the app end the home partition using the key from RAM&lt;BR /&gt;and the command "integritysetup open" and copy the data from SD&lt;BR /&gt;card to eMMC&lt;BR /&gt;6. we close the app and the home partition&lt;/P&gt;&lt;P&gt;When we later boot from eMMC, the key is loaded and decrypted and the protected partitions are mounted.&lt;/P&gt;&lt;P&gt;The question is, when can we burn the fuses, in particular the "secure boot" fuse such that the unique, per device key is used for integrity protection?&lt;/P&gt;&lt;P&gt;If we do that before encrypting the key using the command "caam_tool enc", will the caam tool detect that the device is a secure device? I think it will not, because the device only becomes a secure device after power cycling.&lt;/P&gt;&lt;P&gt;So how can I create a secure device AND use per-device key for integrity protection without having to power cycle the device twice during the installation process?&lt;/P&gt;&lt;P&gt;The web page &lt;A href="https://github.com/f-secure-foundry/caam-keyblob/" target="_blank"&gt;https://github.com/f-secure-foundry/caam-keyblob/&lt;/A&gt; says:&lt;BR /&gt;"The secure operation of the CAAM and SNVS, in production deployments, should always be paired with Secure Boot activation."&lt;/P&gt;&lt;P&gt;Does this always requires an addition power cycling of the board before installing data on the secure partition?&lt;/P&gt;&lt;P&gt;Best regards:&lt;/P&gt;&lt;P&gt;Uwe Fechner&lt;/P&gt;</description>
      <pubDate>Fri, 28 May 2021 11:05:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-install-data-on-integrity-protected-partitions-during/m-p/1284123#M174676</guid>
      <dc:creator>ufechner</dc:creator>
      <dc:date>2021-05-28T11:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: How install data on integrity protected partitions during production using i.MX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-install-data-on-integrity-protected-partitions-during/m-p/1293647#M175614</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Uwe&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;from team:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;------------&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Yes. Secure boot need a new power cycle to enable. CAAM key blob only can be decapsulated in the same life cycle as it is created. So additional power cycle is need.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;------------&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 00:10:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-install-data-on-integrity-protected-partitions-during/m-p/1293647#M175614</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2021-06-17T00:10:29Z</dc:date>
    </item>
  </channel>
</rss>

