METHODS FOR FIRMWARE SIGNATURE

• US 20120005480A1
• Filed: 07/01/2010
• Published: 01/05/2012
• Est. Priority Date: 07/01/2010
• Status: Active Grant

• Current Assignee: Rockwell Automation Technologies Incorporated (Allen-Bradley Co., Inc.)
• Original Assignee: Rockwell Automation Technologies Incorporated (Allen-Bradley Co., Inc.)
• Inventors: Batke, Brian A., Kay, James J., Cook, William B., Visoky, Jack M., Mintz, Scott A.
• Granted Patent: US 8,484,474 B2
• Time in Patent Office: Days
• US Class Current: 713/175
• CPC Class Codes: G05B 19/058 Safety, monitoring
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]
• CPC Class Codes: G06F 2221/033 Test or assess software
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57

Abstract

A method for installing embedded firmware is provided. The method includes generating one or more firmware file instances and generating one or more digital certificate instances that are separate instances from the firmware file instances. The method includes associating the one or more digital certificate instances with the one or more firmware file instances to facilitate updating signature-unaware modules with signature-aware firmware or to facilitate updating signature-aware modules with signature-unaware firmware.

Claims

1. A method for installing embedded firmware, comprising:

generating one or more firmware file instances;

generating one or more digital certificate instances that are separate instances from the firmware file instances; and

associating the one or more digital certificate instances with the one or more firmware file instances.

2. The method of claim 1, further comprising loading the digital certificate instances from a tool that processes the digital certificate instances in the same manner as the firmware file instances.

3. The method of claim 1, further comprising employing a secure boot load tool to allow signature unaware firmware to be securely loaded.

4. The method of claim 1, further comprising employing feedback mechanisms to ensure that a user has physical access to a module in order to update signature unaware firmware.

5. The method of claim 1, further comprising loading signature-aware modules with unsigned firmware.

6. The method of claim 5, further comprising employing feedback mechanisms to ensure that a user has physical access to a module in order to update signature unsigned firmware.

7. The method of claim 1, further comprising associating separate certificates with multiple binaries in order to sign different portions of components including firmware or user programs.

8. The method of claim 1, the certificate includes a component to identify one or more hardware revisions supported by signed firmware.

9. The method of claim 1, further comprising creating a certificate for unmodified firmware and verifying firmware integrity via an update tool.

10. The method of claim 1, further comprising running older versions of firmware through a signing utility and verifying at least one signature against a binary before loading.

11. The method of claim 10, further comprising employing a proxy module to run the signing utility or verify the at least one signature.

12. A software tool for generating firmware signatures, comprising:

a code generator to produce one or more binary file instances;

a certificate component to generate one or more digital certificate instances that are separate instances from the binary file instances, where at least one digital certificate instance is generated for each binary file instance generated; and

a platform component to link the one or more digital certificate instances with the one or more firmware file instances to facilitate updating industrial control module firmware in a secure manner.

13. The software tool of claim 12, the industrial control module firmware is associated with a controller, a communications module, an input/output module, or a bridge module.

14. The software tool of claim 12, further comprising a component to load the digital certificate instances and the binary file instances according to the same download process.

15. The software tool of claim 12, further comprising a secure boot load component to allow signature unaware firmware to be securely loaded.

16. The software tool of claim 12, further comprising a feedback mechanism to ensure that a user has physical access to a module in order to update signature unaware firmware.

17. The software tool of claim 12, further comprising a component to load signature-aware modules with unsigned firmware.

18. The software tool of claim 17, further comprising a feedback mechanism to ensure that a user has physical access to a module in order to update signature unsigned firmware.

19. A firmware updating system, comprising:

means for generating one or more image file instances;

means for generating one or more digital certificate instances that are separate instances from the image file instances; and

means for associating the one or more digital certificate instances with the one or more firmware file instances to facilitate updating signature-unaware modules with signature-aware firmware or to facilitate updating signature-aware modules with signature-unaware firmware.

20. The firmware updating system of claim 19, further comprising one or more feedback components to facilitate that a firmware update is performed locally.