Question regarding NVM writes for transient EC key updates

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Question regarding NVM writes for transient EC key updates

Jump to solution
361 Views
kennychiu
Contributor II

Hi NXP team,

Chip: OM-SE050 ARD-E Dev Kit

I have the following questions regarding EC key operations:

1. Create EC key
Se05x_API_WriteECKey(session_ctx, NULL, 0, 0x11223344, kSE05x_ECCurve_NIST_P256, NULL, 0, NULL, 0, kSE05x_INS_TRANSIENT, kSE05x_KeyPart_Pair);

 
2.Update EC key
Se05x_API_WriteECKey(session_ctx, NULL, 0, 0x11223344, kSE05x_ECCurve_NA, NULL, 0, NULL, 0, kSE05x_INS_TRANSIENT, kSE05x_KeyPart_Pair);
 

According to AN13483 section 8.1, For transient Secure Objects and for Crypto Objects, any update of the value of the Secure Object is not causing additional flash write operations

However, I noticed in SE-PLUG-TRUST-MW_04.07.00 simw-top/hostlib/hostLib/se05x_03_xx_xx/se05x_APDU_impl.h that Se05x_API_WriteECKey() contains the line: nLog("APDU", NX_LEVEL_WARN, "WriteECKey [] APDU causes NVM Writes");

Could you please clarify whether scenario 2 (updating a transient EC key with curveID = NA) will also cause NVM wear?

Thank you very much for your help.

Labels (1)
Tags (1)
0 Kudos
Reply
1 Solution
295 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @kennychiu ,

 

Thanks for the reaching out! Yes, the statement in AN13483 section 8.1, For transient Secure Objects and for Crypto Objects, any update of the value of the Secure Object is not causing additional flash write operations is correct. so for scenario 2 (updating a transient EC key with curveID = NA) will not cause NVM wear. Please also note Creation and deletion of any Secure Object or Crypto Object is causing flash write operations, even you create an transient Secure Object.

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

 

View solution in original post

0 Kudos
Reply
1 Reply
296 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @kennychiu ,

 

Thanks for the reaching out! Yes, the statement in AN13483 section 8.1, For transient Secure Objects and for Crypto Objects, any update of the value of the Secure Object is not causing additional flash write operations is correct. so for scenario 2 (updating a transient EC key with curveID = NA) will not cause NVM wear. Please also note Creation and deletion of any Secure Object or Crypto Object is causing flash write operations, even you create an transient Secure Object.

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

 

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2262058%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EQuestion%20regarding%20NVM%20writes%20for%20transient%20EC%20key%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2262058%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EHi%20NXP%20team%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EChip%3A%20OM-SE050%20ARD-E%20Dev%20Kit%3C%2FP%3E%3CP%3EI%20have%20the%20following%20questions%20regarding%20EC%20key%20operations%3A%3C%2FP%3E%3CP%3E1.%20Create%20EC%20key%3CBR%20%2F%3E%3CSPAN%3ESe05x_API_WriteECKey(session_ctx%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3ENULL%3C%2FSPAN%3E%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E0%3C%2FSPAN%3E%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E0x11223344%3C%2FSPAN%3E%3CSPAN%3E%2C%20kSE05x_ECCurve_NIST_P256%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3ENULL%3C%2FSPAN%3E%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E0%3C%2FSPAN%3E%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3ENULL%3C%2FSPAN%3E%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E0%3C%2FSPAN%3E%3CSPAN%3E%2C%20kSE05x_INS_TRANSIENT%2C%20kSE05x_KeyPart_Pair)%3B%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E2.Update%20EC%20key%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CSPAN%3ESe05x_API_WriteECKey(session_ctx%2C%20%3CSPAN%20class%3D%22%22%3ENULL%3C%2FSPAN%3E%2C%20%3CSPAN%20class%3D%22%22%3E0%3C%2FSPAN%3E%2C%20%3CSPAN%20class%3D%22%22%3E0x11223344%3C%2FSPAN%3E%2C%20kSE05x_ECCurve_NA%2C%20%3CSPAN%20class%3D%22%22%3ENULL%3C%2FSPAN%3E%2C%20%3CSPAN%20class%3D%22%22%3E0%3C%2FSPAN%3E%2C%20%3CSPAN%20class%3D%22%22%3ENULL%3C%2FSPAN%3E%2C%20%3CSPAN%20class%3D%22%22%3E0%3C%2FSPAN%3E%2C%20kSE05x_INS_TRANSIENT%2C%20kSE05x_KeyPart_Pair)%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EAccording%20to%20AN13483%20section%208.1%2C%20For%20transient%20Secure%20Objects%20and%20for%20Crypto%20Objects%2C%20any%20update%20of%20the%20value%20of%20the%20Secure%20Object%20is%20not%20causing%20additional%20flash%20write%20operations%3C%2FP%3E%3CP%3EHowever%2C%20I%20noticed%20in%20SE-PLUG-TRUST-MW_04.07.00%20simw-top%2Fhostlib%2FhostLib%2Fse05x_03_xx_xx%2Fse05x_APDU_impl.h%20that%20Se05x_API_WriteECKey()%20contains%20the%20line%3A%26nbsp%3B%3CSPAN%3EnLog(%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E%22APDU%22%3C%2FSPAN%3E%3CSPAN%3E%2C%20NX_LEVEL_WARN%2C%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E%22WriteECKey%20%5B%5D%20APDU%20causes%20NVM%20Writes%22%3C%2FSPAN%3E%3CSPAN%3E)%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ECould%20you%20please%20clarify%20whether%20scenario%202%20(updating%20a%20transient%20EC%20key%20with%20curveID%20%3D%20NA)%20will%20also%20cause%20NVM%20wear%3F%3C%2FP%3E%3CP%3EThank%20you%20very%20much%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2262058%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3ESE050%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2262194%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Question%20regarding%20NVM%20writes%20for%20transient%20EC%20key%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2262194%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F248310%22%20target%3D%22_blank%22%3E%40kennychiu%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EThanks%20for%20the%20reaching%20out!%20Yes%2C%20the%20statement%20in%26nbsp%3B%3CSPAN%3EAN13483%20section%208.1%2C%20For%20transient%20Secure%20Objects%20and%20for%20Crypto%20Objects%2C%20any%20update%20of%20the%20value%20of%20the%20Secure%20Object%20is%20not%20causing%20additional%20flash%20write%20operations%20is%20correct.%20so%20for%26nbsp%3Bscenario%202%20(updating%20a%20transient%20EC%20key%20with%20curveID%20%3D%20NA)%20will%20not%20cause%20NVM%20wear.%20Please%20also%20note%26nbsp%3BCreation%20and%20deletion%20of%20any%20Secure%20Object%20or%20Crypto%20Object%20is%20causing%20flash%20write%20operations%2C%20even%20you%20create%20an%26nbsp%3Btransient%20Secure%20Object.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EHave%20a%20great%20day%2C%3CBR%20%2F%3EKan%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E-------------------------------------------------------------------------------%3CBR%20%2F%3ENote%3A%3CBR%20%2F%3E-%20If%20this%20post%20answers%20your%20question%2C%20please%20click%20the%20%22Mark%20Correct%22%20button.%20Thank%20you!%3CBR%20%2F%3E-%20We%20are%20following%20threads%20for%207%20weeks%20after%20the%20last%20post%2C%20later%20replies%20are%20ignored%3CBR%20%2F%3EPlease%20open%20a%20new%20thread%20and%20refer%20to%20the%20closed%20one%2C%20if%20you%20have%20a%20related%20question%20at%20a%20later%20point%20in%20time.%3CBR%20%2F%3E-------------------------------------------------------------------------------%3C%2FP%3E%0A%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E