s32k3 basic secure boot, how's the root of trust?

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

s32k3 basic secure boot, how's the root of trust?

跳至解决方案
1,246 次查看
victory
Contributor V

从文档中看是修改IVT的BOOT_SEQ,进入安全启动。那如果别人再修改flash中的IVT,去掉BOOT_SEQ,是否就可以绕过安全启动,从bootloader开始就是篡改的代码了?

Based on the documentation, it seems that modifying the BOOT_SEQ in the IVT enables secure boot. However, if someone else modifies the IVT in the flash memory and removes the BOOT_SEQ, could they bypass secure boot and start running tampered code from the bootloader?

标记 (1)
0 项奖励
回复
1 解答
1,224 次查看
davidtosenovjan
NXP TechSupport
NXP TechSupport

HSE offers functionality for this:

‘The IVT can protect the IVT content to against unauthorized changes based on the service “BOOT_DATA_SIGN”, which works like the BSB mode. The authentication tag is computed and appended to the end of the IVT. To enable IVT authentication, the one-time programmable HSE system attribute IVT_AUTH must be set to 1.’

在原帖中查看解决方案

0 项奖励
回复
1 回复
1,225 次查看
davidtosenovjan
NXP TechSupport
NXP TechSupport

HSE offers functionality for this:

‘The IVT can protect the IVT content to against unauthorized changes based on the service “BOOT_DATA_SIGN”, which works like the BSB mode. The authentication tag is computed and appended to the end of the IVT. To enable IVT authentication, the one-time programmable HSE system attribute IVT_AUTH must be set to 1.’

0 项奖励
回复