Method for identifying the validity of an executable file description by appending the checksum and the version ID of the file to an end thereof

• US 5,991,774 A
• Filed: 12/22/1997
• Issued: 11/23/1999
• Est. Priority Date: 12/22/1997
• Status: Expired due to Fees

• Current Assignee: Schneider Automation Incorporated (Schneider Electric SE)
• Original Assignee: Schneider Automation Incorporated (Schneider Electric SE)
• Inventors: Tate, Allan R., Saylor, Michael J, Grosser, John T.
• Primary Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/995,711
• Time in Patent Office: 701 Days
• Field of Search: 707/203, 707/200, 707/202, 707/201, 707/8, 395/712, 395/703, 395/704, 395/181, 395/184.01
• US Class Current: 707/697
• CPC Class Codes: G06F 11/006 Identification G06F11/2289 takes precedence
• CPC Class Codes: G06F 11/10 Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
• 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
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A method for uniquely identifying a file, along with its particular version ID, used in an application program by a central processing unit provides a system for file security. The method computes a CRC for a file and then appends a version string and CRC at the end of the file according to its version ID. The added CRC/version record information is non-destructive. Once appended, the record will be transported with the file when ever it is moved or copied. CRC allows the integrity of the file to be verified at any time and is used to detect viruses or corrupted or tampered files at startup and also during runtimes of the file and its associated application. The operating system will store the new file length in a file allocation table and will also copy a file seal with the file. When used with a set of files for a particular installation, the file seal provides a unique bill of materials to identify the exact file contents of the particular installation. Down loadable files will then be compared with the allocation table to verify the version of the files and will provide error messages if they are not compatible with the installed system base.

Claims

1. A method for checking integrity of a file used in the execution of an application program, the application program for use by a central processing unit (CPU) having an operating system, the method comprising:

A. computing a checksum record for the file before installing said file in the application program;

B. generating a sealing string for the file, the sealing string including the checksum record of said file and any optional records;

C. appending the sealing string to an end of said file;

D. generating a listing of all applicable files pertinant to the operation of said application program, said listing including the sealing string of the file, said listing accessible by said CPU;

E. installing said appended file in the application program;

F. processing said installed file to decode its appended sealing string; and

verifying a binary integrity of said file;

G. preventing operation of said application program if said binary integrity fails.

2. The method of claim 1 wherein said checksum record is a cyclic redundancy check or CRC calculation.

3. The method of claim 2 wherein one of said optional records in the sealing string is a version record for said file, said version string identifying a particular version of said file, said version label to prevent operation of said application program if it does not compare with a version label stored in said applicable files listing.

4. The method of claim 3 further including means for identifying various attributes of said file, including status of a series of logic switches associated with said file.

5. The method of claim 4 wherein said attribute is a logic switch C indicating that the file has a checksum appended to the end of the file.

6. The method of claim 4 wherein said attribute is a logic switch M marking that the file has been sealed with a checksum, providing that the CRC is correct.

7. The method of claim 4 wherein said attribute is a logic switch L locking the file that has been sealed with a checksum.

8. The method of claim 4 wherein processing said installed file to decode its appended sealing string and comparing it with the stored sealing string is initiated at system startup of said application program.