<?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: NT3H2x11 authentication limit behaviour in NFC</title>
    <link>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830620#M11470</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope you are doing well. As mentioned on the &lt;A href="https://www.nxp.com/docs/en/data-sheet/NT3H2111_2211.pdf" target="_blank"&gt;DataSheet&lt;/A&gt;, As soon as this internal counter reaches the number 2AUTHLIM, any further negative password authentication leads to a &lt;STRONG&gt;permanent locking of the protected part&lt;/STRONG&gt; of the memory for the specified access modes. Independently, &lt;STRONG&gt;whether the provided password is correct or not, each subsequent PWD_AUTH fails&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Ricardo&lt;/P&gt;</description>
    <pubDate>Tue, 19 Mar 2024 02:14:17 GMT</pubDate>
    <dc:creator>Ricardo_Zamora</dc:creator>
    <dc:date>2024-03-19T02:14:17Z</dc:date>
    <item>
      <title>NT3H2x11 authentication limit behaviour</title>
      <link>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830367#M11465</link>
      <description>&lt;P&gt;Hi, I'm designing with the #NT3H2111/#NT3H2211&lt;/P&gt;&lt;P&gt;There is a register AUTHLIM that can be used to limit negative authentication attempts.&lt;/P&gt;&lt;P&gt;Page39 of the datasheet:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;8.7.2 Limiting negative verification attempts &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;To prevent brute-force attacks on the password, the maximum allowed number of negative password authentication attempts can be set using AUTHLIM. This mechanism is disabled by setting AUTHLIM to a value of 000b, which is also the initial state of NTAG I2C plus. &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;If AUTHLIM is not equal to 000b, each negative authentication verification is internally counted. As soon as this internal counter reaches the number 2AUTHLIM, any further negative password authentication leads to a permanent locking of the protected part of the memory for the specified access modes. Independently, whether the provided password is correct or not, each subsequent PWD_AUTH fails. &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;Any successful password verification, before reaching the limit of negative password verification attempts, resets the internal counter to zero. &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So here is my question:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How permanent is the locking of the protected part of the memory?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this "permanent locking" until the device (power-on-)reset ? Or until the next time a NFC-device (smartphone) is presenting itself?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Or is it really permanent turning the device useless?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I cannot find the answer in the datasheet or AN11786.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 14:21:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830367#M11465</guid>
      <dc:creator>Paul_PVS</dc:creator>
      <dc:date>2024-03-18T14:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: NT3H2x11 authentication limit behaviour</title>
      <link>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830620#M11470</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope you are doing well. As mentioned on the &lt;A href="https://www.nxp.com/docs/en/data-sheet/NT3H2111_2211.pdf" target="_blank"&gt;DataSheet&lt;/A&gt;, As soon as this internal counter reaches the number 2AUTHLIM, any further negative password authentication leads to a &lt;STRONG&gt;permanent locking of the protected part&lt;/STRONG&gt; of the memory for the specified access modes. Independently, &lt;STRONG&gt;whether the provided password is correct or not, each subsequent PWD_AUTH fails&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Ricardo&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 02:14:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830620#M11470</guid>
      <dc:creator>Ricardo_Zamora</dc:creator>
      <dc:date>2024-03-19T02:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: NT3H2x11 authentication limit behaviour</title>
      <link>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830926#M11472</link>
      <description>&lt;P&gt;Hi Ricardo,&lt;/P&gt;&lt;P&gt;Thank you for your answer.&amp;nbsp; Can you then confirm the following conclusion:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In applications where an accredited user in possession of a valid password must be able to write in the protected memory, the use of the AUTHLIM feature can lead to sabotage through brute force techniques. This would result in the definitive destruction of the device, as the accredited user would no longer be able to use it afterward due to the permanent locking of the protected part of the memory, which cannot be reversed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this correct? (in which case we will not be able to use this feature - a possibility to reset the permanent locking only by the I2C-side would have been the better solution)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Paul.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 07:47:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1830926#M11472</guid>
      <dc:creator>Paul_PVS</dc:creator>
      <dc:date>2024-03-19T07:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: NT3H2x11 authentication limit behaviour</title>
      <link>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1831309#M11474</link>
      <description>&lt;P&gt;Hi Paul,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, your understanding is correct. After reaching the AUTHLIM, the protected part of the memory will be in a permanent locking, that cannot be reversed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Ricardo&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 16:25:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NT3H2x11-authentication-limit-behaviour/m-p/1831309#M11474</guid>
      <dc:creator>Ricardo_Zamora</dc:creator>
      <dc:date>2024-03-19T16:25:42Z</dc:date>
    </item>
  </channel>
</rss>

