# US 2010/0169654 A1 · Method for author verification and software authorization

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0169654 A1
- Document ID: US20100169654A1
- Status: Published application
- Kind: A1
- Application number: 12/651,085
- Filed: 2009-12-31
- Published: 2010-07-01
- Earliest claimed: 2006-03-01
- Assignees: NVIDIA Corporation
- Inventors: Jeffrey T. Kiel; Andrei Leonid Osnovich
- Web page: https://patentgrep.com/patent/US20100169654A1

## CPC

- H04L 9/3247: {involving digital signatures}
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- H04L 9/3236: {using cryptographic hash functions}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of the present invention are directed to a computer-implemented method for author verification and authorization of object code. In one embodiment, program object code is linked with a plurality of data blocks to create linked object code and a MAP file. Thereafter, author verification is performed by executing a plurality of comparisons between the linked object code and the MAP file. In another embodiment, a digital signing procedure is performed on linked object code by creating a signature data block. The signature data block is then encrypted and written to the linked object code to create digitally-signed object code. In another embodiment, an application program embodied in linked object code generates a data packet. The data packet is then compared to a previously-generated signature data packet from the linked object code to determine if the linked object code is authorized.

## Claims

### Claim 1

A computer-implemented method of verifying object code, said method comprising:
linking program object code with a plurality of data blocks, wherein said linking creates linked object code and an associated map file; and
executing an authorization of said linked object code upon execution of said linked object code, wherein said authorization comprises performing a plurality of comparisons of said linked object code with said associated map file.

### Claim 2 (depends on 1)

The method of claim 1, wherein at least one of said plurality of comparisons is performed at a driver layer.

### Claim 3 (depends on 1)

The method of claim 1, wherein said plurality of comparisons comprises comparing a creation time of said linked object code with a creation time of said associated map file.

### Claim 4 (depends on 1)

The method of claim 1, wherein said plurality of comparisons comprises comparing a portion of a portable executable header of said liked object code with said associated map file.

### Claim 5 (depends on 1)

The method of claim 1, wherein said plurality of comparisons comprises comparing at least one of said plurality of data blocks with said associated map file.

### Claim 6

A computer-implemented method of authorizing object code, said method comprising:
linking program object code with a plurality of function object codes, wherein said linking produces linked object code;
performing a digital signing procedure of said linked object code comprising:
creating a first signature data block comprising information about said linked object code and a computer-system identifier of a computer system authorized to operate said linked object code;
encrypting said first signature data block; and
writing said first encrypted signature data block to said linked object code to create a digitally-signed object code.

### Claim 7 (depends on 6)

The method of claim 6 further comprising:
executing a plurality of said function object codes, wherein said plurality of function object codes execute a method comprising:
creating a second signature data block comprising information about said linked object code and a computer-system identifier of a computer system performing said executing;
encrypting said second signature data block;
reading said first encrypted signature data block from said linked object code; and
comparing said first and second encrypted signature data blocks to determine if said digitally-signed object code is authorized.

### Claim 8 (depends on 6)

The method of claim 6, wherein said information about said linked object code comprises a digest of said linked object code and a redundancy check of a plurality of code pages of said linked object code.

### Claim 9 (depends on 8)

The method of claim 8, wherein said executing a plurality of said function object codes further comprises:
determining a location in a memory where said plurality of said function object codes is executing; and
reading said digest of said linked object code to determine if said location relates to one of said plurality of code pages.

### Claim 10 (depends on 6)

The method of claim 6, wherein said performing a digital signing procedure further comprises modifying an insertion point of said plurality of said function object codes such that said plurality of said function object codes execute prior to any portions of said linked program object code.

### Claim 11 (depends on 6)

The method of claim 6, wherein said performing a digital signing procedure further comprises:
performing a redundancy check on said first encrypted signature data block, wherein said redundancy check produces a first checksum; and
writing said first checksum to said linked object code.

### Claim 12 (depends on 11)

The method of claim 11, wherein said executing a plurality of said function object codes further comprises:
reading said first encrypted signature data block from said linked object code;
performing a redundancy check on said first encrypted signature data block read from said linked object code, wherein said redundancy check produces a second checksum; and
determining that said linked object code is not authorized if said first checksum and said second checksum do not match.

### Claim 13 (depends on 7)

The method of claim 7, wherein said comparing is executed at a driver layer.

### Claim 14

A computer-readable medium having computer-readable program code embodied therein for causing a computer system to perform a method of verifying object code, said method comprising:
linking program object code with a plurality of data blocks, wherein said linking creates linked object code and an associated map file; and
executing an authorization of said linked object code upon execution of said linked object code, wherein said authorization comprises performing a plurality of comparisons of said linked object code with said associated map file.

### Claim 15 (depends on 14)

The computer-readable medium of claim 14, wherein at least one of said plurality of comparisons is performed at a driver layer.

### Claim 16 (depends on 14)

The computer-readable medium of claim 14, wherein said plurality of comparisons comprises comparing a creation time of said linked object code with a creation time of said associated map file.

### Claim 17 (depends on 14)

The computer-readable medium of claim 14, wherein said plurality of comparisons comprises comparing a portion of a portable executable header of said liked object code with said associated map file.

### Claim 18 (depends on 14)

The computer-readable medium of claim 14, wherein said plurality of comparisons comprises comparing at least one of said plurality of data blocks with said associated map file.

### Claim 19

A computer-readable medium having computer-readable program code embodied therein for causing a computer system to perform a method of authorizing object code, said method comprising:
linking program object code with a plurality of function object codes, wherein said linking produces linked object code;
performing a digital signing procedure of said linked object code comprising:
creating a first signature data block comprising information about said linked object code and a computer-system identifier of a computer system authorized to operate said linked object code;
encrypting said first signature data block; and
writing said first encrypted signature data block to said linked object code to create a digitally-signed object code.

### Claim 20 (depends on 19)

The computer-readable medium of claim 19 further comprising:
executing a plurality of said function object codes, wherein said plurality of function object codes execute a method comprising:
creating a second signature data block comprising information about said linked object code and a computer-system identifier of a computer system performing said executing;
encrypting said second signature data block;
reading said first encrypted signature data block from said linked object code; and
comparing said first and second encrypted signature data blocks to determine if said digitally-signed object code is authorized.

### Claim 21 (depends on 19)

The computer-readable medium of claim 19, wherein said information about said linked object code comprises a digest of said linked object code and a redundancy check of a plurality of code pages of said linked object code.

### Claim 22 (depends on 21)

The computer-readable medium of claim 21, wherein said executing a plurality of said function object codes further comprises:
determining a location in a memory where said plurality of said function object codes is executing; and
reading said digest of said linked object code to determine if said location relates to one of said plurality of code pages.

### Claim 23 (depends on 19)

The computer-readable medium of claim 19, wherein said performing a digital signing procedure further comprises modifying an insertion point of said plurality of said function object codes such that said plurality of said function object codes execute prior to any portions of said linked program object code.

### Claim 24 (depends on 19)

The computer-readable medium of claim 19, wherein said performing a digital signing procedure further comprises:
performing a redundancy check on said first encrypted signature data block, wherein said redundancy check produces a first checksum; and
writing said first checksum to said linked object code.

### Claim 25 (depends on 24)

The computer-readable medium of claim 24, wherein said executing a plurality of said function object codes further comprises:
reading said first encrypted signature data block from said linked object code;
performing a redundancy check on said first encrypted signature data block read from said linked object code, wherein said redundancy check produces a second checksum; and
determining that said linked object code is not authorized if said first checksum and said second checksum do not match.

### Claim 26 (depends on 20)

The computer-readable medium of claim 20, wherein said comparing is executed at a driver layer.
