Method for interposing a security function in a computer program

• US 5,542,045 A
• Filed: 03/03/1995
• Issued: 07/30/1996
• Est. Priority Date: 10/15/1993
• Status: Expired due to Fees

• Current Assignee: Rainbow Technologies, Inc. (Thales SA)
• Original Assignee: Software Security, Inc. (Thales SA)
• Inventors: Levine, Anatoli
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): HUA, LY
• Application Number:
  US08/400,285
• Time in Patent Office: 515 Days
• Field of Search: 395/575, 395/325, 395/400, 395/600, 395/650, 395/186, 395/187.01, 395/188.01, 395/700, 395/600, 380/3, 380/4
• US Class Current: 726/11
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 9/4486 Formation of subprogram jump address
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A developer writing a software program provides security for the program being prepared by interposing a special security layer in front of the standard library being utilized for writing the program. A security header and security file are incorporated in the software which automatically reroutes standard library calls through the special security layer prior to putting the calls through to the standard library files.

Claims

1. A method of protecting a developer'"'"'s software without requiring a source code modification on the part of the developer comprising the steps of:

interposing by the developer a security layer furnished by another in front of standard library files being utilized for writing a software program, which security layer incorporates a header, said header including a statement which is placed as the first statement of said software program, creating a path to a standard library file through a security file which is the security function in library form already compiled into said software program to implement security for said software program each time a call is made to said standard library file, whereby

said security layer automatically reroutes standard library calls through said security layer to the standard library file.

2. The method according to claim 1, wherein said security header file includes function definitions the same as a definition of said standard library file definitions, wherein calls to said standard library file result in a security function being performed, and following said security function, said standard library functions are called.

3. A method of protecting a developer'"'"'s software which includes a plurality of standard library files, without requiring a source code modification, comprising:

interposing a security header file in said developer'"'"'s software, said header file defining a path for each call to one of said standard library files;

interposing a security file in each path which provides a security function in a library of said software, said security function controlling operation of said software program by verifying authorization of said program execution; and

passing control to said library files following verification of said authorization.

4. The method of claim 3, wherein a header statement is placed in said software which identifies said security header file.

5. The method of claim 3, wherein said security file identifies and creates two instructions for each call to said one library file, the first to perform said authorization verification and subsequently invokes said one standard library file.

6. A method of protecting software that includes a plurality of standard library files, each standard library file including a plurality of standard library functions, the method comprising the steps of:

providing a security file including a library of security functions;

incorporating a statement referring to a header, the header including a reference to a security function included in the security file, the security function corresponding to a standard library function, into the software;

incorporating the header referred to by the statement into the software;

creating a path to a standard library function through the corresponding security function determined in tile header;

verifying, with the security function, authorization of program execution; and

,

passing control of execution of the software to the standard library function following verification of the authorization.

7. The method of claim 6, wherein the step of creating a path to a standard library function comprises the steps of:

providing a security function including an authorization, verification portion and a reference to a standard library function portion; and

replacing references to standard library functions in the developer'"'"'s software with references to corresponding security functions.