METHODS AND SYSTEMS FOR BYPASSING AUTHENTICITY CHECKS FOR SECURE CONTROL MODULES

• US 20140181526A1
• Filed: 12/20/2012
• Published: 06/26/2014
• Est. Priority Date: 12/20/2012
• Status: Active Grant

• Current Assignee: GM Global Technology Operations LLC (General Motors Company)
• Original Assignee: GM Global Technology Operations LLC (General Motors Company)
• Inventors: ALRABADY, ANSAF I., BALTES, KEVIN M., FOREST, THOMAS M., ROSA, J. DAVID, WIST, ALAN D.
• Granted Patent: US 10,038,565 B2
• Time in Patent Office: Days
• US Class Current: 713/176
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]
• CPC Class Codes: H04L 2209/84 Vehicles
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3249 using RSA or related signature schemes, e.g. Rabin scheme

Abstract

Methods and systems are provided for bypassing an authenticity check for a secure control module. In one embodiment, a method includes: receiving authenticity data from a secure source, wherein the authenticity data includes a signature and an identifier that is unique to the control module; programming the control module with the authenticity data; and bypassing the authenticity check of a control program of the control module based on the authenticity data.

Claims

1. A method of bypassing an authenticity check for a secure control module, comprising:

receiving authenticity data from a secure source, wherein the authenticity data includes a signature and an identifier (ID) that is unique to the control module;

programming the control module with the authenticity data; and

bypassing the authenticity check of a control program of the control module based on the authenticity data.

2. The method of claim 1, further comprising combining the authenticity data with at least one file of the control program, and wherein the programming the control module with the authenticity data comprises programming the control module with the at least one file and the authenticity data.

3. The method of claim 2, wherein the bypassing the authenticity check of the control program comprises selectively bypassing the authenticity check of the control program when the signature of the authenticity data is valid and when the ID matches an identifier of the control module.

4. The method of claim 1, wherein the programming the control module with the authenticity data comprises storing the authenticity data as an authenticity application program in application memory.

5. The method of claim 4, further comprising running the authenticity application program to erase a production boot program from boot memory and write a development boot program to boot memory.

6. The method of claim 5, wherein the bypassing the authenticity check of the control program is performed by the development boot program.

7. The method of claim 6, wherein the bypassing the authenticity check of the control program comprises selectively bypassing the authenticity check of the control program when the signature of the authenticity data is valid and when the ID matches an identifier of the control module.

8. The method of claim 1, wherein the programming the control module with the authenticity data comprises storing the authenticity data in a designated memory location.

9. The method of claim 8, wherein the bypassing the authenticity check of the control program comprises selectively bypassing the authenticity check of the control program when the authenticity data is stored in the designated memory location.

10. The method of claim 9, wherein the bypassing the authenticity check of the control program further comprises selectively bypassing the authenticity check of the control program further when the signature of the authenticity data is valid and when the ID matches an identifier of the control module.

11. The method of claim 8, wherein the designated memory location is in calibration memory.

12. The method of claim 8, wherein the designated memory location is in a memory location that is not part of application memory and calibration memory.

13. The method of claim 1 wherein the authenticity data is programmed to the control module in the form of a file header.

14. The method of claim 1 wherein the authenticity data is programmed to the control module in the form of an application program.

15. The method of claim 1 wherein the authenticity data is programmed to the control module in the form of a security ticket.

16. A system for bypassing an authenticity check, comprising:

a secure control module that includes non-volatile memory; and

a control program that includes authenticity data that is received from a secure source, that stores the authenticity data in the non-volatile memory, and that bypasses the authenticity check of a control program based on the authenticity data, wherein the authenticity data includes a signature and an identifier (ID) that is unique to the control module.

17. The system of claim 16, wherein the non-volatile memory is partitioned into at least boot memory, application memory, and calibration memory, and wherein the authenticity data is stored in application memory.

18. The system of claim 16, wherein the non-volatile memory is partitioned into at least boot memory, application memory, and calibration memory, and wherein the authenticity data is stored in calibration memory.

19. The system of claim 16, wherein the non-volatile memory is partitioned into at least boot memory, application memory, calibration memory, and authenticity memory, and wherein the authenticity data is stored in the authenticity memory.