<?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 Re: How to read CSEc keys in S32K</title>
    <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1812509#M31896</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/227252"&gt;@xiongsl&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;SDK won't support RSA2048 because there's no such hardware feature on CSEc.&lt;BR /&gt;And there's no way to store such key to the CSEc. Nonvolatile keys can't be exported from CSEc. This would violate SHE specification. Only RAM key can be exported if plain key attribute is cleared. &lt;BR /&gt;So, the only option I can see in case of S32K1 device is to emulate this function by software (like wolfssl) and store the key in normal flash. &lt;BR /&gt;Regards,&lt;BR /&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Wed, 21 Feb 2024 06:35:00 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2024-02-21T06:35:00Z</dc:date>
    <item>
      <title>How to read CSEc keys</title>
      <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1812424#M31886</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;My software needs to support RSA2048, but the SDK doesn't support it yet.&lt;/P&gt;&lt;P&gt;If the key is stored to CSEc, how can I read the key so that the software can complete the digital signature?&lt;/P&gt;&lt;P&gt;Key length is 256 bytes.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 04:40:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1812424#M31886</guid>
      <dc:creator>xiongsl</dc:creator>
      <dc:date>2024-02-21T04:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to read CSEc keys</title>
      <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1812509#M31896</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/227252"&gt;@xiongsl&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;SDK won't support RSA2048 because there's no such hardware feature on CSEc.&lt;BR /&gt;And there's no way to store such key to the CSEc. Nonvolatile keys can't be exported from CSEc. This would violate SHE specification. Only RAM key can be exported if plain key attribute is cleared. &lt;BR /&gt;So, the only option I can see in case of S32K1 device is to emulate this function by software (like wolfssl) and store the key in normal flash. &lt;BR /&gt;Regards,&lt;BR /&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 06:35:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1812509#M31896</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2024-02-21T06:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to read CSEc keys</title>
      <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813298#M31944</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/37795"&gt;@lukaszadrapa&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In other words, only the 16-byte key of RAM_KEY supports reading. KEY_01~KEY_17 does not support reading, so the RSA2048 key can only be stored in FLASH or EEPROM.&lt;BR /&gt;Regards,&lt;BR /&gt;xiongsl&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 02:27:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813298#M31944</guid>
      <dc:creator>xiongsl</dc:creator>
      <dc:date>2024-02-22T02:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to read CSEc keys</title>
      <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813305#M31946</link>
      <description>&lt;P&gt;Can the attributes of KEY_01~KEY_17 be cleared and changed to something like RAM_KEY?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 02:35:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813305#M31946</guid>
      <dc:creator>xiongsl</dc:creator>
      <dc:date>2024-02-22T02:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: How to read CSEc keys</title>
      <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813447#M31959</link>
      <description>&lt;P&gt;No, such changes can't be done in CSEc.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 06:07:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813447#M31959</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2024-02-22T06:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to read CSEc keys</title>
      <link>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813456#M31960</link>
      <description>&lt;P&gt;Okay, thanks for the answer.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 06:12:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-read-CSEc-keys/m-p/1813456#M31960</guid>
      <dc:creator>xiongsl</dc:creator>
      <dc:date>2024-02-22T06:12:01Z</dc:date>
    </item>
  </channel>
</rss>

