Light-weight validation of native images

• US 9,584,877 B2
• Filed: 06/16/2011
• Issued: 02/28/2017
• Est. Priority Date: 06/16/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hanna, Fadi, Nagarkar, Pracheeti, Rayhelson, Michael, Kanamori, Atsushi, Biswas, Surupa, Kotas, Jan
• Primary Examiner(s): KUDDUS, DANIEL A
• Application Number:
  US13/161,607
• Publication Number:
  US 20120323858A1
• Time in Patent Office: 2,084 Days
• Field of Search: 707/687, 707/955, 707/999.103
• US Class Current: 1/1
• CPC Class Codes: H04N 21/8153 comprising still images, e.g. texture, background image
• CPC Class Codes: H04N 21/835 Generation of protective data, e.g. certificates protecting software against unauthorised usage in a vending or licensing environment G06F21/10
• CPC Class Codes: H04N 21/84 Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73

Abstract

One or more identifiers that facilitate efficient native image validation can be generated and stored in an auxiliary file upon pre-compiling of an assembly. The native image can be validated against an assembly from which the native image is generated, among other files that influence the generated contents of the native image, based upon the auxiliary file and included identifiers. Additionally, native image validation can be performed in an increasing cost sequence associated with each identifier included within the auxiliary file.

Claims

1. A method comprising:

employing at least one processor configured to execute computer-executable instructions stored in memory to perform the following acts;

receiving metadata created during pre-compilation of intermediate language code of an assembly to a native image, wherein the metadata includes multiple identifiers that capture identifying information regarding the assembly from which the native image was produced and comprise one or more of a last modified timestamp, module version, strong name hash, or targeted patch band attribute;

comparing a version of an assembly with the multiple identifiers sequentially, based on an increasing order of resource utilization to perform a comparison with a particular identifier, until the version of the assembly is determined to correspond to the native image based on one of the multiple identifiers or the comparing is performed with all of the multiple identifiers; and

identifying the native image as valid when the version of the assembly is determined to correspond to the native image and otherwise identifying the native image as invalid.

2. The method of claim 1 further comprises comparing the version of the assembly with the multiple identifiers at runtime.

3. The method of claim 1, validating the native image further comprises receiving the metadata from a location proximate to the native image.

4. The method of claim 1 further comprises employing a common language runtime to compare the version of the assembly with the multiple identifiers.

5. The method of claim 1 further comprises comparing the version of an assembly with a subsequent identifier after comparison with a proceeding identifier fails in determining that the version of the assembly corresponds to the native image.

6. A system comprising:

a hardware processor coupled to a memory, the hardware processor configured to execute computer-executable instructions stored in the memory that when executed perform the following acts;

receives multiple validation identifiers from an auxiliary file created during pre-compilation of intermediate language code of an assembly to a native image, wherein the multiple validation identifiers capture identifying information regarding the assembly from which the native image was produced and comprise one or more of a last modified timestamp, a module version, a strong name hash, or a targeted patch band attribute;

compares a version of an assembly with the multiple validation identifiers sequentially, based on an increasing order of resource utilization to perform a comparison with a particular validation identifier, until the version of the assembly is determined to correspond to the native image based on one of the multiple validation identifiers or the comparing is performed with all of the multiple validation identifiers; and

identifies the native image as valid when the version of the assembly is determined to correspond to the native image and otherwise identifies the native image as invalid.

7. The system of claim 6, the auxiliary file includes the last modified timestamp and at least one of the module version, the strong name hash, or the targeted patch band attribute.

8. The system of claim 7 further comprises an instruction that when executed loads the native image at runtime if the native image is valid.

9. The system of claim 7 further comprises an instruction that when executed compares the last modified timestamp included with the auxiliary file with a last modified timestamp associated with the assembly to ascertain validity of the native image.

10. The system of claim 9, the last modified timestamp associated with the assembly is acquired by at least one of a file system or an operating system.

11. The system of claim 7, the last modified timestamp and the at least one of the module version, the strong name hash, or the targeted patch band attribute is located in the auxiliary file, proximate to the native image.

12. The system of claim 7, the increasing order of resource utilization is the last modified timestamp, the module version, and the targeted patch band attribute for the assembly that does not include a strong name hash.

13. The system of claim 7, the increasing order of resource utilization is the last modified timestamp, the strong name hash, and the targeted patch band attribute for the assembly that includes a strong name hash.

14. The system of claim 7, the assembly includes code with a plurality of virtual instructions that are translated to create the native image with native instructions executable by a host machine.

15. A computer-readable storage device having instructions stored thereon that upon execution of the instructions by at least one processor perform a method, the method comprising:

receiving multiple validation identifiers from an auxiliary file created during pre-compilation of intermediate language code of an assembly generating a native image, wherein the multiple validation identifiers capture identifying information regarding the assembly from which the native image was produced and comprise at least one of a last modified timestamp, module version, strong name hash, or targeted patch band attribute;

comparing a version of an assembly with the multiple validation identifiers sequentially, based on an increasing order of resource utilization to perform a comparison with a particular validation identifier, until the version of the assembly is determined to correspond to the native image based on one of the multiple validation identifiers or the comparing is performed with all of the multiple validation identifiers; and

identifying the native image as valid when the version of the assembly is determined to correspond to the native image and otherwise identifying the native image as invalid.

16. The computer-readable storage device of claim 15, the method further comprises comparing the version of the assembly with the multiple validation identifiers in the following order:

last modified timestamp, module version, strong name hash, and targeted patch band attribute.

17. The computer-readable storage device of claim 16, the method further comprises comparing the version of the assembly with a subsequent identifier after comparison with a proceeding identifier fails in determining that the version of the assembly corresponds to the native image.