Ensuring that a software update may be installed or run only on a specific device or class of devices

• US 20050132357A1
• Filed: 05/01/2004
• Published: 06/16/2005
• Est. Priority Date: 12/16/2003
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Curtis, Diane, Shell, Scott R., Fortier, Dominique
• Application Number:
  US10/837,151
• Publication Number:
  US 20050132357A1
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs
• CPC Class Codes: G06F 21/51 at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]
• CPC Class Codes: G06F 21/575 Secure boot
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user

Abstract

Described is a system and method in which a system and method in which a device manufacturer or software image provider controls which devices are allowed to install or to run a software image. An image keying mechanism uses package data and UUID associated with the device or class of devices to key an image. Because the UUID is used in the key, an installer verifier and/or boot-time verifier can ensure that the device is authorized to install and/or run the image. Any package, including existing device packages or the package for which installation is requested can demand that keying be enforced. An installer mechanism checks whether the device is allowed to install the image. A boot-time enforcement mechanism prevents an improperly installed image from operating by halting the boot process if a demanded key is invalid or missing.

Claims

1. In a computing environment, a method comprising:

identifying a device set containing a device or class of devices for which an image entity comprising an image or a subcomponent of an image is to be keyed; and

securely associating an identifier corresponding to the device set with the image entity such that an enforcement mechanism associated with a device of the set can determine whether the image entity is allowed to run on that associated device.

2. The method of claim 1 wherein identifying the device set for which the image entity is to be keyed comprises providing a UUID associated with the device set to a server that keys the image entity.

3. The method of claim 2 wherein the server keys the image entity by obtaining a first hash of data corresponding to the image entity, obtaining a second hash of the UUID, combining the first and second hashes, signing the combined first and second hashes to produce a key, and associating the key with the image entity.

4. The method of claim 3 wherein the image entity comprises a package, and wherein obtaining a first hash of data corresponding to the image entity comprises obtaining a hash corresponding to the package.

5. The method of claim 3 wherein obtaining a hash corresponding to the package comprises obtaining a hash of a device manifest file that describes the package.

6. The method of claim 3 wherein the enforcement mechanism checks the key by obtaining a first hash of data corresponding to the image entity, obtaining a second hash of the UUID, combining the first and second hashes, and signing the combined first and second hashes to produce a second key to compare with the key associated with the image entity.

7. The method of claim 3 wherein the enforcement mechanism is implemented in an installer, and wherein the enforcement mechanism determines whether the image entity is allowed to run on the device set by preventing installation unless the key is valid for the device set and the image entity.

8. The method of claim 7 further comprising, verifying, in a secure boot process, validity of boot loader code that boots the device, and verifying in the boot loader code, validity of the installer that contains the enforcement mechanism.

9. The method of claim 3 wherein the enforcement mechanism is implemented in a device boot process, and wherein the enforcement mechanism determines whether the image entity is allowed to run on the associated device by preventing booting of the associated device unless, for at least some of the subcomponents of the image entity, there is a key which is valid for the associated device.

10. The method of claim 9 further comprising, verifying, in a secure boot process, the validity of the code that contains the enforcement mechanism.

11. The method of claim 1 wherein the enforcement mechanism determines whether the image entity is allowed to run on the associated device by checking a key associated with a subcomponent of the image that is based on the an identifier corresponding to the associated device of the set.

12. The method of claim 11 wherein the enforcement mechanism operates in response to a keying demand.

13. The method of claim 11 wherein the keying demand is obtained with the image entity.

14. The method of claim 11 wherein the keying demand is obtained from a file corresponding to another package that has a corresponding image already installed on the associated device.

15. The method of claim 11 wherein the keying demand is obtained from a file corresponding to another package that is to be processed for installing data onto the associated device.

16. The method of claim 11 wherein the key is obtained from a signed hash, the signed hash comprising a first hash of data corresponding to the image and second hash of the identifier corresponding to the associated device.

17. The method of claim 16 wherein the identifier corresponding to the device is an identifier for a class of devices.

18. The method of claim 16 wherein the data corresponding to the image comprises a description of a package containing the image.

19. One or more computer-readable media having computer-executable instructions which when executed perform the method of claim 1.

20. In a computing environment, a system comprising:

a keying mechanism that signs a package with a key, the key based on a data corresponding to the package and data corresponding to the first device identifier; and

an enforcement mechanism associated with a device that has a second device identifier which may or may not be the same as the first device identifier used by the keying mechanism, the enforcement mechanism determining based on the key and the second device identifier whether an image corresponding to contents of the package is allowed to run on the device having the second device identifier.

21. The system of claim 20 wherein the first and second identifiers are each in the form of a UUID associated with a device or a class of devices.

22. The system of claim 20 wherein the data corresponding to the package is a hash of a file in the package that describes the package.

23. The system of claim 20 wherein the data corresponding to the first device identifier is a hash of a UUID of the first device identifier.

24. The system of claim 20 wherein the data corresponding to the package is a hash of a file in the package that describes the package, the data corresponding to the first device identifier is a hash of a UUID of the first device identifier and wherein the keying mechanism signs a concatenation of the hashes.

25. The system of claim 20 wherein the enforcement mechanism comprises an install time verifier that prevents the image from running or allows the image to run by preventing installation or allowing installation based on a comparison of the key against a value computed with the second identifier value.

26. The system of claim 20 wherein the enforcement mechanism comprises a boot time verifier that prevents the device booting or allows the device to boot based on a comparison of the key against a value computed with the second identifier value.

27. The system of claim 20 wherein the enforcement mechanism checks the key by obtaining a first hash of data corresponding to the package, obtaining a second hash of the UUID, combining the first and second hashes, and signing the combined first and second hashes to produce a signature to compare with the key associated with the package.

28. The system of claim 20 wherein the enforcement mechanism operates in response to a keying demand.

29. The system of claim 28 wherein the keying demand is obtained with the package.

30. The system of claim 28 wherein the keying demand is obtained from a file corresponding to another package that has a corresponding image already installed on the associated device.

31. The system of claim 28 wherein the keying demand is obtained from a file corresponding to another package that is to be processed for installing data onto the associated device.

32. The system of claim 20 wherein the first identifier corresponding to the device is an identifier for a class of devices.

33. The system of claim 20 wherein the first and second identifiers are identical.

34. The system of claim 20 further comprising means for verifying validity of the enforcement mechanism prior to running the enforcement mechanism.

35. The system of claim 20 wherein the enforcement mechanism comprises a boot-time verifier, and wherein the means for the verifying validity of the enforcement mechanism comprises a secure boot mechanism in device hardware.

36. The system of claim 20 wherein the enforcement mechanism comprises an install-time verifier, and wherein the means for the verifying validity of the enforcement mechanism comprises code in a boot loader that loads the code containing the install-time verifier.