<?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 Code Signing Tool (CST) with existing DEK? in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Code-Signing-Tool-CST-with-existing-DEK/m-p/2051128#M234449</link>
    <description>&lt;P&gt;I am configuring encrypted boot for an i.MX8 ULP board. I'm using instructions from here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://raw.githubusercontent.com/nxp-imx/uboot-imx/refs/heads/lf_v2024.04/doc/imx/ahab/guides/mx8ulp_9x_encrypted_boot.txt" target="_blank"&gt;https://raw.githubusercontent.com/nxp-imx/uboot-imx/refs/heads/lf_v2024.04/doc/imx/ahab/guides/mx8ulp_9x_encrypted_boot.txt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The CST tool generates a new Data Encryption Key (DEK) every time it is run, encrypts the container and saves the key in the file specified in the .csf file, overwriting any existing key.&amp;nbsp; I want to be able to sign my containers using an existing DEK for which I have already generated the dek_blob.&lt;/P&gt;&lt;P&gt;How is that possible?&lt;/P&gt;</description>
    <pubDate>Tue, 25 Feb 2025 22:14:40 GMT</pubDate>
    <dc:creator>ddresser</dc:creator>
    <dc:date>2025-02-25T22:14:40Z</dc:date>
    <item>
      <title>Code Signing Tool (CST) with existing DEK?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Code-Signing-Tool-CST-with-existing-DEK/m-p/2051128#M234449</link>
      <description>&lt;P&gt;I am configuring encrypted boot for an i.MX8 ULP board. I'm using instructions from here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://raw.githubusercontent.com/nxp-imx/uboot-imx/refs/heads/lf_v2024.04/doc/imx/ahab/guides/mx8ulp_9x_encrypted_boot.txt" target="_blank"&gt;https://raw.githubusercontent.com/nxp-imx/uboot-imx/refs/heads/lf_v2024.04/doc/imx/ahab/guides/mx8ulp_9x_encrypted_boot.txt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The CST tool generates a new Data Encryption Key (DEK) every time it is run, encrypts the container and saves the key in the file specified in the .csf file, overwriting any existing key.&amp;nbsp; I want to be able to sign my containers using an existing DEK for which I have already generated the dek_blob.&lt;/P&gt;&lt;P&gt;How is that possible?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2025 22:14:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Code-Signing-Tool-CST-with-existing-DEK/m-p/2051128#M234449</guid>
      <dc:creator>ddresser</dc:creator>
      <dc:date>2025-02-25T22:14:40Z</dc:date>
    </item>
  </channel>
</rss>

