User Tools

Site Tools


manual:security

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:security [2018/07/03 15:52]
voorburg [Security]
manual:security [2018/07/04 14:47]
voorburg [Bootloader]
Line 17: Line 17:
 The next step is to configure the location of the seed/key shared library in Microboot. The demo programs are preconfigured to work with the one called "​libseednkey.dll"​. This file is located in the same directory as Microboot. Follow these steps: The next step is to configure the location of the seed/key shared library in Microboot. The demo programs are preconfigured to work with the one called "​libseednkey.dll"​. This file is located in the same directory as Microboot. Follow these steps:
  
-  * Start Microboot by double-clicking "​\Host\**MicroBoot.exe**"​. +  * Start Microboot by double-clicking "​\Host\**MicroBoot.exe**" ​(on Linux it is "​\Host\**MicroBoot**"​)
-  * Click the "​**Settings**"​-button and, on the newly appeared dialog, ​click the "**Options**"-button+  * Click the "​**Settings**"​-button and, on the newly appeared dialog, ​go to the "Session Protocol"-tab
-  * On the "XCP Protection"​-tab ​Click the "​**Browse**"​-button and select the file "​libseednkey.dll"​. +  * Click the "​**Browse**"​-button and select the file "​libseednkey.dll"​. 
-  * Click "​**OK**" ​twice to save the settings.+  * Click "​**OK**"​ to save the settings.
  
-{{:manual:microboot_xcp_protection.png?nolink|}}+{{:manual:microboot_xcp_seedkey_protection.png?|}}
  
 If you now perform a firmware update, everything will work as usual. The moment you remove the "​libseednkey.dll"​-file or if it contains an invalid security unlock algorithm, firmware updates will be rejected by the bootloader. If you now perform a firmware update, everything will work as usual. The moment you remove the "​libseednkey.dll"​-file or if it contains an invalid security unlock algorithm, firmware updates will be rejected by the bootloader.
Line 58: Line 58:
 blt_int8u XcpVerifyKeyHook(blt_int8u resource, blt_int8u *key, blt_int8u len) blt_int8u XcpVerifyKeyHook(blt_int8u resource, blt_int8u *key, blt_int8u len)
 { {
-  /* the example key algorithm in "FeaserKey.dll" works as follows:+  /* the example key algorithm in "libopenblt.dll" works as follows:
    ​* ​ - programming resource will be unlocked if key = seed - 1    ​* ​ - programming resource will be unlocked if key = seed - 1
    */    */
manual/security.txt · Last modified: 2022/02/10 19:10 by voorburg