<?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 do I generate MACt() to activate the SAM AV3? in Secure Authentication</title>
    <link>https://community.nxp.com/t5/Secure-Authentication/How-do-I-generate-MACt-to-activate-the-SAM-AV3/m-p/1562867#M1018</link>
    <description>&lt;P&gt;To active the SAM AV3, I receive a random number Rnd2 (12) bytes in length, returned from the SAM_LockUnlock() command with P1 set to ‘011.’&amp;nbsp; I now need to send SAM_LockUnlockPart2 with Rnd1 (which I generate) along with MACHost.&amp;nbsp; MACHost is 8 bytes, defined by MACt() of Kx, Rnd1, P1_Part1, plus 3 additional parameters and ZeroPad.&lt;/P&gt;&lt;P&gt;MACt(key,message) is the even numbered matrix state array elements of an AES computation, defined in section 10 of ds323531.&amp;nbsp; MACing references NIST Special Publication 800-38B, which I’m looking at.&amp;nbsp; Somehow, the definition of MACt() tosses out the 4 parameters and ZeroPad and introduces a 16 byte state array from AES128.&lt;/P&gt;&lt;P&gt;I don’t know how we make this leap.&amp;nbsp; I assume Kx is the default key of the SAM, I generate Rnd1,… then [something happens] and I’m taking 8 of the 16 byte transformed state array of AES128.&amp;nbsp; I’m missing the remaining steps to generate MACt().&amp;nbsp; I’m putting in 4 parameters, what I assume is the default SAM key, but this does not line up with the state array of AES… unless I run the AES128 encryption on… [something]?&lt;/P&gt;&lt;P&gt;Is there any way to activate the SAM without AES encryption and MACt generation?&amp;nbsp; If not, can someone tell me the missing steps? (assuming I'm a newb without much AES128 encryption experience)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Dec 2022 14:18:18 GMT</pubDate>
    <dc:creator>Henry3</dc:creator>
    <dc:date>2022-12-01T14:18:18Z</dc:date>
    <item>
      <title>How do I generate MACt() to activate the SAM AV3?</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/How-do-I-generate-MACt-to-activate-the-SAM-AV3/m-p/1562867#M1018</link>
      <description>&lt;P&gt;To active the SAM AV3, I receive a random number Rnd2 (12) bytes in length, returned from the SAM_LockUnlock() command with P1 set to ‘011.’&amp;nbsp; I now need to send SAM_LockUnlockPart2 with Rnd1 (which I generate) along with MACHost.&amp;nbsp; MACHost is 8 bytes, defined by MACt() of Kx, Rnd1, P1_Part1, plus 3 additional parameters and ZeroPad.&lt;/P&gt;&lt;P&gt;MACt(key,message) is the even numbered matrix state array elements of an AES computation, defined in section 10 of ds323531.&amp;nbsp; MACing references NIST Special Publication 800-38B, which I’m looking at.&amp;nbsp; Somehow, the definition of MACt() tosses out the 4 parameters and ZeroPad and introduces a 16 byte state array from AES128.&lt;/P&gt;&lt;P&gt;I don’t know how we make this leap.&amp;nbsp; I assume Kx is the default key of the SAM, I generate Rnd1,… then [something happens] and I’m taking 8 of the 16 byte transformed state array of AES128.&amp;nbsp; I’m missing the remaining steps to generate MACt().&amp;nbsp; I’m putting in 4 parameters, what I assume is the default SAM key, but this does not line up with the state array of AES… unless I run the AES128 encryption on… [something]?&lt;/P&gt;&lt;P&gt;Is there any way to activate the SAM without AES encryption and MACt generation?&amp;nbsp; If not, can someone tell me the missing steps? (assuming I'm a newb without much AES128 encryption experience)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Dec 2022 14:18:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/How-do-I-generate-MACt-to-activate-the-SAM-AV3/m-p/1562867#M1018</guid>
      <dc:creator>Henry3</dc:creator>
      <dc:date>2022-12-01T14:18:18Z</dc:date>
    </item>
  </channel>
</rss>

