Part Number: CC1310
i'm able to successfully use the various ECC functions in the cc1310 ROM -- to generate a pair of keys, to sign/verify a message, and to compute a shared secret....
my application also requires that my host (PC, cloud, etc) be able verify that a particular cc1310 is authentic... assume the host is running a standard environment such as node.js and has the public key associated with that particular cc1310 in question.... following standard convention, the host would send some known (but random) number to the cc1310; and the cc1310 would return a SHA256 hash of this number signed with its private key.... the host would then verify the signature using the same hash of the number but with the public key.... nothing unusual here....
the question i have is about the *format* of the two-part signature produced by ECC_ECDSA_sign().... output from the latter function is a pair of 32-byte buffers; but signatures generated on my host (using standard node.js crypto functions) are 71 bytes in length.... does anyone have an example of verifying a cc1310-generated signature on *any* host computer under *any* environment.... if so, i can probably figure out the rest....
bob.
