<?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>i.MX ProcessorsのトピックIssues with meta-nxp-security-reference-design</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1906458#M226090</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I just started to work on adding secure boot to my project (irst time and lot of reading). In the Linux User Guide, IMXLUG_6.6.23_2.0.0, from June 28 2024, section &lt;STRONG&gt;10.9.1.3 Yocto setup for secure boot build&lt;/STRONG&gt;, you cannot follow the steps due to a lacking manifest.&lt;/P&gt;&lt;P&gt;Also, when I manually added the layer, the nxp-cst-signer.bb&amp;nbsp; is pointing towards&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;CST_SIGNER ?= "git://git@bitbucket.sw.nxp.com/imxs/cst-signer.git;protocol=ssh"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;which I assume is a place where I should not have access. I guess it might be ok to point it towards&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;https://github.com/nxp-imx-support/nxp-cst-signer.git&lt;/LI-CODE&gt;&lt;P&gt;instead?&lt;/P&gt;&lt;P&gt;Is there a way to report such things, or is the forum the place to go? Are you using githubs issue tracker?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jul 2024 16:17:43 GMT</pubDate>
    <dc:creator>malj</dc:creator>
    <dc:date>2024-07-11T16:17:43Z</dc:date>
    <item>
      <title>Issues with meta-nxp-security-reference-design</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1906458#M226090</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I just started to work on adding secure boot to my project (irst time and lot of reading). In the Linux User Guide, IMXLUG_6.6.23_2.0.0, from June 28 2024, section &lt;STRONG&gt;10.9.1.3 Yocto setup for secure boot build&lt;/STRONG&gt;, you cannot follow the steps due to a lacking manifest.&lt;/P&gt;&lt;P&gt;Also, when I manually added the layer, the nxp-cst-signer.bb&amp;nbsp; is pointing towards&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;CST_SIGNER ?= "git://git@bitbucket.sw.nxp.com/imxs/cst-signer.git;protocol=ssh"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;which I assume is a place where I should not have access. I guess it might be ok to point it towards&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;https://github.com/nxp-imx-support/nxp-cst-signer.git&lt;/LI-CODE&gt;&lt;P&gt;instead?&lt;/P&gt;&lt;P&gt;Is there a way to report such things, or is the forum the place to go? Are you using githubs issue tracker?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 16:17:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1906458#M226090</guid>
      <dc:creator>malj</dc:creator>
      <dc:date>2024-07-11T16:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with meta-nxp-security-reference-design</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1907359#M226138</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/193642"&gt;@malj&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for contacting NXP Support!&lt;/P&gt;
&lt;P&gt;I have reviewed the case and currently, I'm checking with the team for possible solutions.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 19:26:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1907359#M226138</guid>
      <dc:creator>brian14</dc:creator>
      <dc:date>2024-07-12T19:26:03Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with meta-nxp-security-reference-design</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1910075#M226250</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/193642"&gt;@malj&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for your report, the expert team will fix the link.&lt;/P&gt;
&lt;P&gt;In the meantime, you can use the GitHub link. &lt;BR /&gt;git://github.com/nxp-imx-support/nxp-cst-signer.git;protocol=https&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2024 21:20:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Issues-with-meta-nxp-security-reference-design/m-p/1910075#M226250</guid>
      <dc:creator>brian14</dc:creator>
      <dc:date>2024-07-16T21:20:39Z</dc:date>
    </item>
  </channel>
</rss>

