METHOD TO REPLACE BOOTLOADER PUBLIC KEY

• US 20130111203A1
• Filed: 07/24/2012
• Published: 05/02/2013
• Est. Priority Date: 10/28/2011
• Status: Active Grant

• Current Assignee: GM Global Technology Operations LLC (General Motors Company)
• Original Assignee: GM Global Technology Operations LLC (General Motors Company)
• Inventors: FOREST, THOMAS M., ALRABADY, ANSAF I., BALTES, KEVIN M., COSTIN, MARK H.
• Granted Patent: US 9,021,246 B2
• Time in Patent Office: Days
• US Class Current: 713/100
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: H04L 2209/84 Vehicles
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A system and method for writing a new or replacement public key to a bootloader stored in a memory segment in the memory of a vehicle ECU without having to rewrite the entire bootloader. The method includes defining a key table in the bootloader memory segment includes a number of vacant memory slots that are available to store replacement public keys if they are needed. The key table is a separate section of the bootloader memory segment so that the key table memory slots are not used by the bootloader code.

Claims

1. A method for replacing a public key in a bootloader stored in a controller, said method comprising:

defining a bootloader memory segment in a memory in the controller that the bootloader will be stored in;

defining a key table in the bootloader memory segment that includes a plurality of available memory slots for storing public keys;

storing an original public key in a first memory slot in the key table and leaving the rest of the memory slots in the key table empty; and

storing a replacement public key in a next memory slot below a last stored public key in the key table.

2. The method according to claim 1 further comprising determining whether a request to store a replacement key is valid before storing the replacement key.

3. The method according to claim 1 wherein storing the original public key in a first memory slot includes setting a validity flag to valid in the first memory slot, and setting all of the other memory slots in the key table to invalid.

4. The method according to claim 3 wherein storing the replacement public key in a next memory slot includes setting the validity flag for the next memory slot to valid.

5. The method according to claim 1 wherein storing a replacement public key includes determining whether the replacement public key is the same as a public key stored in the last memory slot in the key table that includes a public key and determining whether the validity flag for that memory slot is set to valid.

6. The method according to claim 5 further comprising setting the validity flag to valid if the replacement public key is the same as the public key already in the last memory slot and if the valid flag had been set to invalid.

7. The method according to claim 1 further comprising erasing the entire key table if all of the memory slots in the key table are full and it is necessary to replace the public key.

8. The method according to claim 1 wherein the public key is used in an asymmetric key cryptography process for securely flashing programs into the controller that includes a process for hashing a content file to be stored in the controller and verifying a digital signature of the hash of the content file using the public key.

9. The method according to claim 1 wherein the controller is an electronic control unit (ECU) on a vehicle.

10. A method for replacing a public key in a bootloader stored in a memory of an electronic control unit (ECU) on a vehicle, said method comprising:

defining a bootloader memory segment in a memory in the ECU that the bootloader will be stored in;

defining a key table in the bootloader memory segment that includes a plurality of available memory slots for storing public keys;

storing an original public key in a first memory slot in the key table and leaving the rest of the memory slots in the key table empty;

setting a validity flag associated with the first memory slot in the key table to valid and setting all other validity flags associated with the empty slots to invalid;

storing a replacement public key in a next memory slot below the last stored public key in the key table; and

setting the validity flag for the next memory slot to valid once the replacement public key is stored.

11. The method according to claim 10 wherein storing a replacement public key includes determining whether the replacement public key is the same as a public key stored in the last memory slot in the key table that includes a public key and determining whether the validity flag for that memory slot is set to valid.

12. The method according to claim 10 further comprising setting the validity flag to valid if the replacement public key is the same as the public key already in the last memory slot and if the validity flag had been set to invalid.

13. The method according to claim 10 further comprising erasing the entire key table if all of the memory slots in the key table are full and it is necessary to replace the public key.

14. The method according to claim 10 wherein the public key is used in an asymmetric key cryptography process for securely flashing programs into the controller that includes a process for hashing a content file to be stored in the controller and verifying a digital signature of the hash of the content file using the public key.

15. A system for replacing a public key in a bootloader stored in a controller, said system comprising:

means for defining a bootloader memory segment in a memory in the controller that the bootloader will be stored in;

means for defining a key table in the bootloader memory segment that includes a plurality of available memory slots for storing public keys;

means for storing an original public key in a first memory slot in the key table and leaving the rest of the memory slots in the key table empty; and

means for storing an replacement public key in a next memory slot below a last stored public key in the key table.

16. The system according to claim 15 wherein the means for storing the original public key in a first memory slot sets a validity flag to valid in the first memory slot, and sets all of the other memory slots in the key table to invalid.

17. The system according to claim 16 wherein the means for storing the replacement public key in a next memory slot sets the validity flag for the next memory slot to valid.

18. The system according to claim 15 wherein the means for storing a replacement public key determines whether the replacement public key is the same as a public key stored in the last memory slot in the key table that includes a public key and determines whether the validity flag for that memory slot is set to valid.

19. The system according to claim 18 further comprising setting the validity flag to valid if the replacement public key is the same as the public key already in the last memory slot and if the validity flag had been set to invalid.

20. The system according to claim 15 wherein the public key is used in an asymmetric key cryptography process for securely flashing programs into the controller that includes a process for hashing a content file to be stored in the controller and verifies a digital signature of the hash of the content file using the public key.