Is there any way in iMX6 to have Encryption/decryption mechanism unique per SOC

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

Is there any way in iMX6 to have Encryption/decryption mechanism unique per SOC

跳至解决方案
1,288 次查看
swapnilpendhare
Contributor III

Hi

As mentioned in earlier discussion Dose Data encryption done with help of black blob involve hardware key? , its clear that the Black blob generated with help of hardware key would be unique across boards; but encrypted data is going to be same if the black blob used for encryption , is created from same user key across boards.

Is there any way to generate unique encrypted data per SOC?

标签 (1)
0 项奖励
回复
1 解答
863 次查看
Yuri
NXP Employee
NXP Employee

Hello,

  The unique OTP Master Key (OTPMK) is used to encrypt and wrap the DEK (Data Encryption Key) in a blob.
The OTMPK is protected by the hardware and can be accessed only by CAAM. Consequently, this step has to
be executed on the target processor with software capable of using CAAM. 

  The fact that the OTPMK can only be accessed by CAAM means that the blob can only be decrypted by the
same processor that encrypted it. To further add to the security of the DEK, the blob is decapsulated and decrypted
inside a secure memory partition that can only be accessed by CAAM.


Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

在原帖中查看解决方案

1 回复
864 次查看
Yuri
NXP Employee
NXP Employee

Hello,

  The unique OTP Master Key (OTPMK) is used to encrypt and wrap the DEK (Data Encryption Key) in a blob.
The OTMPK is protected by the hardware and can be accessed only by CAAM. Consequently, this step has to
be executed on the target processor with software capable of using CAAM. 

  The fact that the OTPMK can only be accessed by CAAM means that the blob can only be decrypted by the
same processor that encrypted it. To further add to the security of the DEK, the blob is decapsulated and decrypted
inside a secure memory partition that can only be accessed by CAAM.


Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------