Provisioning, upgrading, and/or changing of hardware

• US 8,966,657 B2
• Filed: 12/31/2009
• Issued: 02/24/2015
• Est. Priority Date: 12/31/2009
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Martinez, Alberto J., Stevens, William A. Jr., Goel, Purushottam, Brickell, Ernie
• Primary Examiner(s): HOLDER, BRADLEY W
• Application Number:
  US12/655,579
• Publication Number:
  US 20110161672A1
• Time in Patent Office: 1,881 Days
• Field of Search: 713/176, 726/30
• US Class Current: 726/30
• 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/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 9/3249 using RSA or related signature schemes, e.g. Rabin scheme

Abstract

In some embodiments a secure permit request to change a hardware configuration is created. The secure permit request is sent to a remote location, and a permit sent from the remote location in response to the permit request is received. The hardware configuration is changed in response to the received permit. Other embodiments are described and claimed.

Claims

1. A method comprising:

creating, by a management engine in a system a secure permit request for a permit to change a hardware configuration of a hardware component of the system having a processor, wherein the hardware configuration is a hardware configuration of a chipset or a chipset part, wherein the secure permit request includes permit authentication information to bind the permit to the system, wherein a unique key has been permanently programmed into the hardware component by randomly blowing fuses in the hardware component during manufacturing, and wherein the management engine is capable of running services separate from a controller in the system;

sending the secure permit request to a remote location, wherein the unique key is used to ensure secure communication and permit authentication with the remote location;

receiving, by the management engine, a permit message sent from the remote location in response to the secure permit request, wherein the permit message includes the permit authentication information; and

changing, by the management engine, the hardware configuration of the hardware component by updating registers in the hardware configuration in response to validating the permit authentication information in the received permit message.

2. The method of claim 1, wherein the secure permit request and the permit protect privacy of a user of the hardware component.

3. The method of claim 1, wherein the secure permit request and the permit protect privacy of the hardware component.

4. The method of claim 1, wherein one or more cryptographic keys are used to ensure secure communication with the remote location.

5. The method of claim 1, wherein the unique key is not accessible by software running outside of the hardware component.

6. The method of claim 1, wherein the permit includes a unique signature from the remote location.

7. The method of claim 1, further comprising validating the received permit using a public key which corresponds to a private signing key located at the remote location.

8. The method of claim 1, wherein the remote location is a secure and trusted location.

9. The method of claim 1, wherein the changing of the hardware configuration is performed without any physical change to the hardware component.

10. The method of claim 1, wherein the permit is a secure permit and/or a signed permit.

11. The method of claim 1, wherein transaction information is bound inside the permit such that future returns or exchanges can be enabled.

12. The method of claim 1, wherein once a permit is signed for a particular hardware part it cannot be used on another hardware part.

13. The method of claim 1, wherein software running outside of the hardware component cannot emulate the functionality of software running inside the hardware component.

14. The method of claim 1, further comprising performing an override during a boot and/or initialization process, and changing the hardware configuration in response to the override.

15. The method of claim 1, wherein the secure permit request is not uniquely identifiable.

16. The method of claim 1, wherein the identity of the hardware component and/or the user of the hardware component is not determinable from the secure permit request.

17. The method of claim 1, further comprising generating a random value and generating the secure permit request in response to the random value.

18. The method of claim 1, wherein the management engine comprises a hardware processing engine separate from the processor in the system.

19. The method of claim 1, wherein the management engine has access to computational resources not accessible to an operating system executed by the processor in the system.

20. The method of claim 1, wherein the management engine configures the hardware component by changing values in hardware fuse override registers in the hardware component.

21. A method comprising:

receiving, at a permit server, from a system at a remote location a secure permit request for a permit to change a hardware configuration of a hardware component of the system at the remote location, wherein the hardware configuration is a hardware configuration of a chipset or a chipset part, wherein a unique key has been permanently programmed into the hardware component by randomly blowing fuses in the hardware component during manufacturing, wherein the unique key is used to ensure secure communication and permit authentication between the permit server and the system at the remote location, and wherein the secure permit request includes permit authentication information to bind the permit to the system; and

sending, by the permit server, a permit message to the system remote location in response to the secure permit request, wherein the permit message includes the permit authentication information, and wherein the permit message is to allow the remote location to change the hardware configuration of the hardware component by updating registers in the hardware configuration in response to validating the permit authentication information in the permit message at the remote location.

22. The method of claim 21, wherein the secure permit request and the permit protect privacy of a user of the hardware component.

23. The method of claim 21, wherein one or more cryptographic keys are used to ensure secure communication and permit authentication with the remote location.

24. The method of claim 21, wherein the permit includes a unique signature.

25. The method of claim 21, wherein the permit is to allow the remote location to change the hardware configuration without any physical change to the hardware component.

26. The method of claim 21, wherein the permit is a secure permit and/or a signed permit.

27. The method of claim 21, wherein the permit is to allow the remote location to change the hardware configuration in response to an override operation performed during a boot and/or initialization process.

28. The method of claim 21, wherein the secure permit request is not uniquely identifiable.

29. The method of claim 21, wherein the identity of the hardware component and/or the user of the hardware component is not determinable from the secure permit request.

30. The method of claim 21, wherein the secure permit request has been created at the remote location in response to a random value.

31. The method of claim 21, further comprising using a private signing key that corresponds to a public key located at the remote location to help in validation of the permit at the remote location.

32. The method of claim 21, wherein transaction information is bound inside the permit such that future returns or exchanges can be enabled.

33. The method of claim 21, wherein once a permit is signed for a particular hardware part it cannot be used on another hardware part.

34. The method of claim 21, wherein software running outside of the hardware cannot emulate the functionality of software running inside the hardware.

35. An apparatus comprising:

a hardware device having a hardware configuration that may be remotely configured, the hardware device including a controller;

to create a secure permit request for a permit to change the hardware configuration of a hardware component, wherein the hardware configuration is a hardware configuration of a chipset or a chipset part, wherein the secure permit request includes permit authentication information to bind the permit to the hardware device,

wherein a unique key has been permanently programmed into the hardware component by randomly blowing fuses in the hardware component during manufacturing;

to send the secure permit request to a remote location, wherein the unique key is used to ensure secure communication and permit authentication with the remote location;

to receive a permit message sent including the permit authentication information from the remote location in response to the secure permit request; and

to change the hardware configuration of the hardware component by updating registers in the hardware configuration in response to validating the permit authentication information in the received permit message.

36. The apparatus of claim 35, further comprising one or more cryptographic keys to ensure secure communication and permit authentication with the remote location.

37. The apparatus of claim 35, wherein the unique key is not accessible by software running outside of the hardware device.

38. The apparatus of claim 35, wherein the permit includes a unique signature from the remote location.

39. The apparatus of claim 35, the controller further to validate the received permit using a public key which corresponds to a private signing key located at the remote location.

40. The apparatus of claim 35, wherein the remote location is a secure and trusted location.

41. The apparatus of claim 35, further comprising the controller to change the hardware configuration without any physical change to the hardware component.

42. The apparatus of claim 35, wherein the permit is a secure permit and/or a signed permit.

43. The apparatus of claim 35, wherein transaction information is bound inside the permit such that future returns or exchanges can be enabled.

44. The apparatus of claim 35, wherein once a permit is signed for a particular hardware device it cannot be used on another hardware device.

45. The apparatus of claim 35, wherein software running outside of the hardware device cannot emulate the functionality of software running inside the hardware device.

46. The apparatus of claim 35, further comprising the controller to perform an override during a boot and/or initialization process, and to change the hardware configuration in response to the override.

47. The apparatus of claim 35, wherein the secure permit request is not uniquely identifiable.

48. The apparatus of claim 35, wherein the identity of the hardware component and/or the user of the hardware component is not determinable from the secure permit request.

49. The apparatus of claim 35, wherein the apparatus includes a processor executing code, and wherein the controller comprises a hardware processing engine separate from the processor.

50. The apparatus of claim 49, wherein the controller has access to computational resources not accessible to an operating system executed by the processor in the system.

51. The apparatus of claim 35, wherein the controller configures the hardware configuration by changing values in hardware fuse override registers in the hardware configuration.

52. An apparatus comprising:

a server including hardware;

to receive from a remote location a secure permit request for a permit to change a hardware configuration of a hardware component of a system at the remote location, wherein the hardware configuration is a hardware configuration of a chipset or a chipset part, wherein a unique key has been permanently programmed into the hardware component by randomly blowing fuses in the hardware component during manufacturing, wherein the unique key is used to ensure secure communication and permit authentication between the permit server and the system at the remote location, and wherein the secure permit request includes permit authentication information to bind the permit to the system; and

to send a permit message to the remote location in response to the secure permit request, wherein the permit message includes the permit authentication information, and wherein the permit is to allow the remote location to change the hardware configuration of the hardware component by updating registers in the hardware configuration in response to the remote location validating the permit authentication information in the permit message.

53. The apparatus of claim 52, wherein one or more cryptographic keys are used to ensure secure communication and permit authentication with the remote location.

54. The apparatus of claim 52, wherein the permit includes a unique signature.

55. The apparatus of claim 52, wherein the permit is to allow the remote location to change the hardware configuration without any physical change to the hardware component.

56. The apparatus of claim 52, wherein the permit is a secure permit and/or a signed permit.

57. The apparatus of claim 52, wherein the permit is to allow the remote location to change the hardware configuration in response to an override operation performed during a boot and/or initialization process.

58. The apparatus of claim 52, wherein the secure permit request is not uniquely identifiable.

59. The apparatus of claim 52, wherein the identity of the hardware component and/or the user of the hardware component is not determinable from the secure permit request.

60. The apparatus of claim 52, wherein the secure permit request has been created at the remote location in response to a random value.

61. The apparatus of claim 52, further comprising the server to use a private signing key that corresponds to a public key located at the remote location to help in validation of the permit at the remote location.

62. The apparatus of claim 52, wherein transaction information is bound inside the permit such that future returns or exchanges can be enabled.

63. The apparatus of claim 52, wherein once a permit is signed for a particular hardware part it cannot be used on another hardware part.

64. The method of claim 52, wherein software running outside of the hardware component cannot emulate the functionality of software running inside the hardware component.