https://devzone.nordicsemi.com/f/nordic-q-a/57246/using-cc310-to-verify-an-secp128r1-signatureWe have a need to verify an secp128r1 ECDSA signature. I see that this is not one of the curves supported by the CC310, but I&#39;m looking into creating the CRYS_ECPKI_Domain_t myself. Most of the members can be easily found as defined by the ECC standarden-USTelligent Community 13Mon, 03 Feb 2020 18:35:18 GMThttps://devzone.nordicsemi.com/thread/232423?ContentTypeID=1Mon, 03 Feb 2020 18:35:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8da5beb0-3825-4555-b846-1735cae66f03juliantbrown<p>Hi Einar,</p> <p>Got it. Thanks for the reply. That is what I suspected, but it is good to know for sure.</p> <p>And understood, we are only using&nbsp;secp128r1 in this case because it is part of a system we are integrating with and we have no option to use a stronger curve. Appreciate your concern.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/232382?ContentTypeID=1Mon, 03 Feb 2020 14:52:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:44993bd4-5213-401a-aac5-29133281b8bfEinar Thorsrud<p>Hi,</p> <p>The CC310 does not support&nbsp;secp128r1. I am not sure if it is theoretically possible for the HW to do it (we have not tested), but unfortunately, we cannot share internal details of the CC310 HW or runtime library. I suspect your best option is to use a SW library such as <a href="http://discovery.csc.ncsu.edu/software/TinyECC/">TinyECC</a>.</p> <p>PS: We do not recommend using secp128r1 as it is not recommended by NIST based on the number of <a href="https://www.keylength.com/en/4/">bits of security</a>.</p><div style="clear:both;"></div>