Source authentication of a software product

• US 9,965,639 B2
• Filed: 07/17/2015
• Issued: 05/08/2018
• Est. Priority Date: 07/17/2015
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bhat, Badekila Ganesh Prashanth, Gokavarapu, Nageswararao V., Kurian, John, Srinivasan, Raghavendran
• Primary Examiner(s): Pham, Luu
• Assistant Examiner(s): Wilcox, James J
• Application Number:
  US14/801,967
• Publication Number:
  US 20170017798A1
• Time in Patent Office: 1,026 Days
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263

Abstract

Embodiments of the present invention provide systems and methods for authenticating the source code of a software end product. The method includes generating a compound key, which is composed of a set of unique keys generated from a source file. A set of files are separately build based on a received source code, and a key generated and embedded into the files at the time of the build. A validation tool is used to compare the values of the generated compound key to the values of the embedded key to determine if the values match.

Claims

1. A method for authenticating source code, the method comprising:

extracting, by one or more processors, source code having at least one source file having at least one reserved field;

generating, by a key generator, a compound key comprising the at least one source file, a hash function run on the at least one source file, and a file size of the at least one source file;

building, by one or more processors, a set of files, based on the source code from the at least one source file;

injecting, by one or more processors, a generated value based on the compound key into each file of the built set of files either as metadata or as an entry in the at least one source file;

comparing, by a key validation tool, the compound key and the generated value to determine if said compound key is equivalent to said generated value;

producing, by one or more processors, a final product, wherein the final product comprises;

the key validation tool and the generated compound key;

determining, by one or more processors, whether there is a difference between the compound key and the generated value; and

in response to determining that there is not a difference between the compound key and the value, loading the final product to a repository.

2. The method of claim 1, wherein comparing, by the key validation tool, the compound key and the value to determine if said compound key is equivalent to said value comprises:

scanning, by the key validation tool, the compound key;

for a compound key entry, searching, by the key validation tool, the set of files for an entry which matches the entry in the compound key; and

responsive to detecting an entry in the set of files which matches the entry in the compound key, comparing a value associated with the entry in the set of files to a value associated with the entry in the compound key, to determine if the value associated with the entry in the set of files is equivalent to the value associated with the entry in the compound key.

3. The method of claim 1, wherein extracting, by one or more processors, source code having at least one source file having at least one reserve field-comprises:

adding, by a manager, a row to the compound key, wherein the row comprises;

a source path; and

information associated with the at least one source file.

4. The method of claim 1, further comprising:

receiving, by a manager, the source code from the at least one source file; and

generating, by the manager, a unique key for the at least one source file, wherein the unique key comprises information associated with the at least one source file.

5. A computer program product for authenticating source code, the computer program product comprising:

a computer readable storage medium and program instructions stored on the computer readable storage medium, the program instructions comprising;

program instructions to extract source code having at least one source file having at least one reserved field;

program instructions to generate a compound key comprising the at least one source file, a hash function run on the at least one source file, and a file size of the at least one source file;

program instructions to build a set of files, based on the source code from the at least one source file;

program instructions to inject a generated value based on the compound key into each file of the built set of files either as metadata or as an entry in the at least one source file;

program instructions to compare the compound key and the value to determine if said compound key is equivalent to said generated value;

program instructions to produce a final product, wherein the final product comprises;

a key validation tool and the generated compound key;

program instructions to determine whether there is a difference between the compound key and the generated value; and

program instructions to, in response to determining that there is not a difference between the compound key and the value, load the final product to a repository.

6. The computer program product of claim 5, wherein the program instructions to compare the compound key and the value to determine if said compound key is equivalent to said value comprise:

program instructions to scan the compound key;

program instructions to, for a compound key entry, search the set of files for an entry which matches the entry in the compound key; and

program instructions to, responsive to detecting an entry in the set of files which matches the entry in the compound key, compare a value associated with the entry in the set of files to a value associated with the entry in the compound key, to determine if the value associated with the entry in the set of files is equivalent to the value associated with the entry in the compound key.

7. The computer program product of claim 5, wherein extracting, by one or more processors, source code having at least one source file having at least one reserve field comprises:

program instructions to add a row to the compound key, wherein the row comprises;

a source path; and

information associated with the at least one source file.

8. The computer program product of claim 5, further comprising:

program instructions to receive the source code from the at least one source file; and

program instructions to generate a unique key for the at least one source file, wherein the unique key comprises information associated with the at least one source file.

9. A system for authenticating source code, the system comprising:

one or more computer processors;

one or more computer readable storage media;

program instructions to extract source code having at least one source file having at least one reserved field;

program instructions to generate a compound key comprising the at least one source file, a hash function run on the at least one source file, and a file size of the at least one source file;

program instructions to build a set of files, based on the source code from the at least one source file;

program instructions to inject a generated value based on the compound key into each file of the built set of files either as metadata or as an entry in the at least one source file;

program instructions to compare the compound key and the value to determine if said compound key is equivalent to said generated value;

program instructions to produce a final product, wherein the final product comprises;

a key validation tool and the generated compound key;

program instructions to determine whether there is a difference between the compound key and the generated value; and

program instructions to, in response to determining that there is not a difference between the compound key and the value, load the final product to a repository.

10. The system of claim 9, wherein the program instructions to compare the compound key and the value to determine if said compound key is equivalent to said value comprise:

program instructions to scan the compound key;

program instructions to, for a compound key entry, search the set of files for an entry which matches the entry in the compound key; and

program instructions to, responsive to detecting an entry in the set of files which matches the entry in the compound key, compare a value associated with the entry in the set of files to a value associated with the entry in the compound key, to determine if the value associated with the entry in the set of files is equivalent to the value associated with the entry in the compound key.

11. The system of claim 9, further comprising:

program instructions to receive the source code from the at least one source file; and

program instructions to generate a unique key for the at least one source file, wherein the unique key comprises information associated with the at least one source file.