Generating an ECC keypair #57
-
Dear all,
This returns error 0x8007, but if I change position with optiga_key_id = OPTIGA_KEY_ID_E0F1; than works fine. Why? Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
If we are talking about generic OPTIGA Trust M chips, they are pre-provisioned by default with a X.509 Certificate and a corresponding private key. You can find more about this either here or here So that certificate is provisioned at 0xe0e0 data slot and the private key is loaded at 0xe0f0. You can't change them generally speaking. it is possible to permanently remove them (only applied for the generic chips on the market) by chaning metadata. 0x8007 error is Access Conditions error, which means that you can't update the object as the change Access Conditions don't allow this. Please have a look at Solutions Reference Manual Table 72 page 104, You have there a Key Object 0xe0f0, the default "Change" Access Condition for this object is "NEV (Never)", which means you can't update this private key (key generation is a key update procedure), but you can do this for other objects. |
Beta Was this translation helpful? Give feedback.
-
Ok! Thanks a lot for your precious help. Best regards, |
Beta Was this translation helpful? Give feedback.
If we are talking about generic OPTIGA Trust M chips, they are pre-provisioned by default with a X.509 Certificate and a corresponding private key. You can find more about this either here or here
So that certificate is provisioned at 0xe0e0 data slot and the private key is loaded at 0xe0f0. You can't change them generally speaking. it is possible to permanently remove them (only applied for the generic chips on the market) by chaning metadata.
0x8007 error is Access Conditions error, which means that you can't update the object as the change Access Conditions don't allow this. Please have a look at Solutions Reference Manual Table 72 page 104,
You have there a Key Object 0xe0f0, the defa…