Method for testing a software shim
AssigneeMicrosoft Corporation
InventorDiaa Fathalla
Life of this patent
Estimating the term…
Abstract
A method for testing a software shim is provided, in which a skeleton executable file is altered so that it mimics the executable file for which the shim is intended. The alterations made to the skeleton executable file may include one or more of the following: changing the file name, padding the file and changing the calculated checksum of the file.
Claims20
A method for simulating a first executable file using a second executable file, the method comprising:
- modifying at least a portion of a header section of the second executable file to match that of the second executable file;
- padding the second executable file to a size approximately equal to a size of the first executable file;
- and
- modifying at least a portion of the second executable file such that checksums of the first and second executable files are equal.
A method for testing a software shim for a first executable file, the method comprising:
- creating a second executable file;
- modifying at least a portion of a header section of the second executable file to match that of the second executable file;
- modifying at least a portion of a resource section of the second executable file to match a corresponding portion of a resource section of the second executable file;
- and
- executing the software shim in conjunction with the second executable file.
A method for temporarily changing the value of a checksum, the method comprising:
- determining the value of a first file's checksum;
- determining a value to which a piece of data of a second file needs to be changed so that the second file's checksum is approximately equal to the first file's checksum;
- storing the piece of data;
- replacing, in the second file, the piece of data with the determined value;
- and
- inserting a line of code into the second file which, when executed, puts the piece of data back into the second file in place of the determined value.
Dependencies are inferred from the claim text.