<?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 Using Easy-Ecc to Verify Originality Signature for NTAG213 in NFC</title>
    <link>https://community.nxp.com/t5/NFC/Using-Easy-Ecc-to-Verify-Originality-Signature-for-NTAG213/m-p/1065325#M7273</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;BR /&gt;I am referring to&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;EM&gt;AN11350 NTAG Originality Signature Validation&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;and the described example to verify an NXP originality signature with lib Easy-Ecc, Chapter 2.2.1.3 C code example.&lt;BR /&gt;I am using a NTAG213 and want to verify the originality signature.&lt;/P&gt;&lt;P&gt;If I exactly do what is described in this chapter, using the pubKey, UID and Sig, the function ecdsa_verify() reports an invalid signature.&lt;BR /&gt;What makes me a bit surprised is that the function ecdsa_verify() expects a key input of size: ECC_BYTES+1, which is 17 in case of the proposed curve secp128r1. The given NXP public key has a length of 33 instead.&lt;BR /&gt;So, does anyone got this going with a successful verification???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To clarify, I am using the pubKey, UID and SIg provided by the application note example for a first test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and best regards&lt;/P&gt;&lt;P&gt;Andreas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Aug 2020 14:48:34 GMT</pubDate>
    <dc:creator>andreas3</dc:creator>
    <dc:date>2020-08-05T14:48:34Z</dc:date>
    <item>
      <title>Using Easy-Ecc to Verify Originality Signature for NTAG213</title>
      <link>https://community.nxp.com/t5/NFC/Using-Easy-Ecc-to-Verify-Originality-Signature-for-NTAG213/m-p/1065325#M7273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;BR /&gt;I am referring to&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;EM&gt;AN11350 NTAG Originality Signature Validation&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;and the described example to verify an NXP originality signature with lib Easy-Ecc, Chapter 2.2.1.3 C code example.&lt;BR /&gt;I am using a NTAG213 and want to verify the originality signature.&lt;/P&gt;&lt;P&gt;If I exactly do what is described in this chapter, using the pubKey, UID and Sig, the function ecdsa_verify() reports an invalid signature.&lt;BR /&gt;What makes me a bit surprised is that the function ecdsa_verify() expects a key input of size: ECC_BYTES+1, which is 17 in case of the proposed curve secp128r1. The given NXP public key has a length of 33 instead.&lt;BR /&gt;So, does anyone got this going with a successful verification???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To clarify, I am using the pubKey, UID and SIg provided by the application note example for a first test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and best regards&lt;/P&gt;&lt;P&gt;Andreas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2020 14:48:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Using-Easy-Ecc-to-Verify-Originality-Signature-for-NTAG213/m-p/1065325#M7273</guid>
      <dc:creator>andreas3</dc:creator>
      <dc:date>2020-08-05T14:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: Using Easy-Ecc to Verify Originality Signature for NTAG213</title>
      <link>https://community.nxp.com/t5/NFC/Using-Easy-Ecc-to-Verify-Originality-Signature-for-NTAG213/m-p/1065326#M7274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Andreas,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Easy-Ecc lib can be used to&amp;nbsp;&lt;SPAN&gt;verify an NXP originality signature as described in AN11350, but some slight modification is needed as well. Due to this information is confidential, please kindly create a private ticket for it. You may refer to&amp;nbsp;&lt;A href="https://community.nxp.com/docs/DOC-329745"&gt;How to submit a new question for NXP Support&lt;/A&gt;&amp;nbsp; for details.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;SPAN&gt;Thanks for your patience and understanding!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&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;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Aug 2020 05:59:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Using-Easy-Ecc-to-Verify-Originality-Signature-for-NTAG213/m-p/1065326#M7274</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2020-08-27T05:59:25Z</dc:date>
    </item>
  </channel>
</rss>

