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

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

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

ソリューションへジャンプ
1,469件の閲覧回数
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,447件の閲覧回数
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,448件の閲覧回数
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 件の賞賛
返信