RENEWABLE INTEGRITY ROOTED SYSTEM

• US 20080256631A1
• Filed: 04/13/2007
• Published: 10/16/2008
• Est. Priority Date: 04/13/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: ZVI, NIR BEN
• Granted Patent: US 8,266,691 B2
• Time in Patent Office: Days
• US Class Current: 726/22
• CPC Class Codes: G06F 21/56 Computer malware detection or handling, e.g. anti-virus arrangements
• CPC Class Codes: G06F 21/565 by checking file integrity
• 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: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures

Abstract

A method of validating software is disclosed. The method may include receiving, at a first function, a first hash and a first version. The first function may validate a second function according to the first hash and first version. The second function may receive a second hash and a second version, and the second function may validate a third function according to the second hash and second version. The first version and first hash may be stored within the first function, for example. The first version and first hash may be stored within a manifest, for example.

In another embodiment, a method of validating software may include storing a plurality of functions and storing a version and hash for each function. Each function may be verified according to the respective version and hash, and each function may verify at least one other function.

Claims

1. A computer-readable storage medium for validating software, the computer-readable storage medium including computer executable instructions to perform the acts comprising:

receiving, at a first function, a first hash and a first version;

validating, by the first function, a second function according to the first hash and the first version;

receiving, at the second function, a second hash and a second version; and

validating, by the second function, a third function according to the second hash and second version.

2. The computer-readable medium of claim 1, wherein the first function provides an operation of the software.

3. The computer-readable medium of claim 1, wherein the first hash and first version are stored within the first function.

4. The computer-readable medium of claim 1, wherein the first version and the first hash are stored in a manifest.

5. The computer-readable medium of claim 4, wherein the manifest is cryptographically signed.

6. The computer-readable medium of claim 1, wherein the first version comprises a range of version numbers.

7. The computer-readable medium of claim 1, further comprising:

receiving, at the first function, a first size; and

validating, by the first function, the second function according to the first size.

8. The computer-readable medium of claim 7, further comprising receiving a starting point wherein the second function may be defined by the starting point and the first size.

9. The computer-readable medium of claim 1, wherein the first function and the second function are stored within a binary file.

10. A method of validating software, comprising:

storing a plurality of functions;

storing a version and hash for each function of the plurality of functions; and

verifying each function according to the respective version and the hash, wherein each function verifies at least one other function.

11. The method of claim 10, wherein the each function of the plurality of functions provides an operation of the software in addition to said validating.

12. The method of claim 10, wherein each respective hash and version are stored within the each respective function of the plurality of functions.

13. The method of claim 10, wherein each respective version and hash are stored in a manifest.

14. The method of claim 13, wherein the manifest is cryptographically signed.

15. The method of claim 10, wherein the first version comprises a range of version numbers.

16. The method of claim 10, further comprising storing a start byte and a size for each function of the plurality of functions.

17. The method of claim 10, where at least two functions of the plurality of functions are stored within the same binary file.

18. A system for validating software comprising:

a processor that processes a plurality of function calls, each function call being processed according to a respective source and verifying a respective target according to a respective version and respective hash; and

a memory unit that stores a plurality of functions and that stores the respective version and respective hash for each function of the plurality of functions, wherein each function of the plurality of functions is defined as a respective source and a respective target.

19. The system of claim 18, wherein the respective version and the respective hash are stored in a manifest.

20. The system of claim 19, wherein the manifest is cryptographically signed.