<?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>NFCのトピックNXP NFC Reader Library - Authentication with two/three possible A keys?</title>
    <link>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1377179#M9017</link>
    <description>&lt;P&gt;With our new reader we are trying to update a sector in a Mifare Classic card.&lt;/P&gt;&lt;P&gt;Problem: We have old mifare cards in which we want to write additional data.&lt;/P&gt;&lt;P&gt;However there are 3 possible keys that have access to Sector 1.&lt;BR /&gt;- The old Mifare classic "A0 A1 A2 A3 A4 A5" key&lt;BR /&gt;- The new Mifare classic "FF FF FF FF FF FF" key&lt;BR /&gt;- Our empty key "01 23 45 67 89 AB" key.&lt;/P&gt;&lt;P&gt;We are now using the NXP NFC Reader Library (in the past a custom library)&lt;BR /&gt;Doing a discovery works perfect.&lt;BR /&gt;Doing a "phalMfc_Authenticate" with the first key (A0..A5) which is right works and data can be read and written.&lt;/P&gt;&lt;P&gt;However when the first "phalMfc_Authenticate" (A0..A5) fails and trying to continue with "phalMfc_Authenticate"&amp;nbsp; (FF..FF) the card always fails as if the key was wrong. But if i start with the second key (FF..FF) it is accepted.&lt;/P&gt;&lt;P&gt;Looking at the datasheet of the MF1S50 (Mifare classic)&amp;nbsp; i don't see the flow to follow with a failure on an Authenticate.&lt;/P&gt;&lt;P&gt;Looking through the NXP NFC Reader Library i don't see the method how to recover from a Authenticate failure.&lt;/P&gt;&lt;P&gt;Do note: i a trying to do this with the NFC reader library without turning off the field and re-doing the anticollision loop. (The Card number is known and sector 0 already has been validated by the program)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Nov 2021 16:06:55 GMT</pubDate>
    <dc:creator>bwinter</dc:creator>
    <dc:date>2021-11-25T16:06:55Z</dc:date>
    <item>
      <title>NXP NFC Reader Library - Authentication with two/three possible A keys?</title>
      <link>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1377179#M9017</link>
      <description>&lt;P&gt;With our new reader we are trying to update a sector in a Mifare Classic card.&lt;/P&gt;&lt;P&gt;Problem: We have old mifare cards in which we want to write additional data.&lt;/P&gt;&lt;P&gt;However there are 3 possible keys that have access to Sector 1.&lt;BR /&gt;- The old Mifare classic "A0 A1 A2 A3 A4 A5" key&lt;BR /&gt;- The new Mifare classic "FF FF FF FF FF FF" key&lt;BR /&gt;- Our empty key "01 23 45 67 89 AB" key.&lt;/P&gt;&lt;P&gt;We are now using the NXP NFC Reader Library (in the past a custom library)&lt;BR /&gt;Doing a discovery works perfect.&lt;BR /&gt;Doing a "phalMfc_Authenticate" with the first key (A0..A5) which is right works and data can be read and written.&lt;/P&gt;&lt;P&gt;However when the first "phalMfc_Authenticate" (A0..A5) fails and trying to continue with "phalMfc_Authenticate"&amp;nbsp; (FF..FF) the card always fails as if the key was wrong. But if i start with the second key (FF..FF) it is accepted.&lt;/P&gt;&lt;P&gt;Looking at the datasheet of the MF1S50 (Mifare classic)&amp;nbsp; i don't see the flow to follow with a failure on an Authenticate.&lt;/P&gt;&lt;P&gt;Looking through the NXP NFC Reader Library i don't see the method how to recover from a Authenticate failure.&lt;/P&gt;&lt;P&gt;Do note: i a trying to do this with the NFC reader library without turning off the field and re-doing the anticollision loop. (The Card number is known and sector 0 already has been validated by the program)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2021 16:06:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1377179#M9017</guid>
      <dc:creator>bwinter</dc:creator>
      <dc:date>2021-11-25T16:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: NXP NFC Reader Library - Authentication with two/three possible A keys?</title>
      <link>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1377911#M9022</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/131765"&gt;@bwinter&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case of authentication failure, the tag/card is back to IDLE state, you need not reset the RF field, just follow the&amp;nbsp;Identification and Selection Procedure as described in&amp;nbsp;Figure 4. MIFARE Classic command flow diagram from the data sheet before issuing authentication command again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that makes sense,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a great day,&lt;BR /&gt;Kan&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;BR /&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 05:08:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1377911#M9022</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2021-11-29T05:08:44Z</dc:date>
    </item>
    <item>
      <title>Re: NXP NFC Reader Library - Authentication with two/three possible A keys?</title>
      <link>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1378190#M9023</link>
      <description>&lt;P&gt;The datasheets of all Classic variants have never been very clear in which state the card is.&lt;BR /&gt;If i take for example the MIFARE Classic EV1 1K (MF1S50YYX_V1) datasheet Figure 4 after the "Select Card" block we can move to the "authentication" block but no path is given when authentication fails (and in which state the card ends).&lt;/P&gt;&lt;P&gt;As wrote above we are working with our new hardware and new firmware using the latest NXP NFC Reader Library (and not an ancient version).&lt;BR /&gt;Digging into our old firmware (with compiled library) pointed to ReAuthent which seems to reselect the card without doing the complete&amp;nbsp; anticollision loop which of course save some time (reading and validating card type and other data blocks already succeeded)&lt;/P&gt;&lt;P&gt;I think i will have to search for the easiest way to do this for the same card with de NXP NFC Reader Library routines.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 12:15:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NXP-NFC-Reader-Library-Authentication-with-two-three-possible-A/m-p/1378190#M9023</guid>
      <dc:creator>bwinter</dc:creator>
      <dc:date>2021-11-29T12:15:33Z</dc:date>
    </item>
  </channel>
</rss>

