OBFUSCATING DEBUGGING FILENAMES

• US 20160170862A1
• Filed: 12/15/2014
• Published: 06/16/2016
• Est. Priority Date: 12/15/2014
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Barkelew, Jonathan Bret, Martinez, Ricardo L.
• Granted Patent: US 9,483,381 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler
• CPC Class Codes: G06F 16/166 File name conversion
• CPC Class Codes: G06F 8/41 Compilation

Abstract

An information handling system, method, and computer-readable media for obfuscating debugging filenames during a software build are described. The system comprises one or more processors, a memory, and one or more program modules stored on the memory and executable by the one or more processors. The one or more program modules compile a source code file of a plurality of source code files into a program, generate a debugging file including debugging information for the program, utilize a one-way deterministic function to generate an obfuscated filename for the debugging file, and include a link to the debugging file in the program, the link including the obfuscated filename.

Claims

1. An information handling system for obfuscating debugging filenames during a software build, the information handling system comprising:

one or more processors;

a memory;

one or more program modules stored on the memory and executable by the one or more processors to;

compile a source code file of a plurality of source code files into a program;

generate a debugging file including debugging information for the program;

utilize a one-way deterministic function to generate an obfuscated filename for the debugging file; and

include a link to the debugging file in the program, the link including the obfuscated filename.

2. The information handling system of claim 1, wherein the one-way deterministic function utilizes at least an original filename of the source code file or the program as an input into the one-way deterministic function to generate the obfuscated filename.

3. The information handling system of claim 2, wherein the one-way deterministic function utilizes at least a cryptographic salt as another input into the one-way deterministic function to generate the obfuscated filename.

4. The information handling system of claim 1, wherein the one or more program modules are further executable by the one or more processors to generate a reverse-lookup file that associates the obfuscated filename with an original filename of the source code file or the program.

5. The information handling system of claim 1, wherein the link to the debugging file in the program includes a directory pathway, wherein links for each of a plurality of debugging files for each of the source code files include the directory pathway.

6. The information handling system of claim 1, wherein the one-way deterministic function is a hash function.

7. The information handling system of claim 1, wherein the one or more program modules are further executable by the one or more processors to:

run a linker module to include the link to the debugging file in the program; and

utilize the one-way deterministic function to generate the obfuscated filename prior to running the linker module.

8. The information handling system of claim 1, wherein the program is one of a plurality of programs included in an executable binary file, wherein the executable binary file includes links to a plurality of debugging files, one debugging file for each of the plurality of programs.

9. The information handling system of claim 8, wherein the executable binary file is a Basic Input/Output System (BIOS) file.

10. A method for obfuscating debugging filenames during a software build, the method comprising:

compiling a source code file of a plurality of source code files into a program, the program included in a Basic Input/Output System (BIOS) file;

generating a debugging file including debugging information for the program;

utilizing a one-way deterministic function to generate an obfuscated filename for the debugging file; and

including a link to the debugging file in the program, the link including the obfuscated filename.

11. The method of claim 10, further comprising utilizing at least an original filename of the source code file or the program as an input into the one-way deterministic function to generate the obfuscated filename.

12. The method of claim 11, utilizing a cryptographic salt as another input into the one-way deterministic function to generate the obfuscated filename.

13. The method of claim 10, further comprising generating a reverse-lookup file that identifies the obfuscated filename with an original filename of the source code file or the program.

14. The method of claim 10, further comprising:

running a linker module to include the link to the debugging file in the program; and

utilizing the one-way deterministic function to generate the obfuscated filename prior to running the linker module.

15. The method of claim 10, wherein the program is one of a plurality of programs included in the BIOS file, wherein the BIOS file includes links to a plurality of debugging files, one debugging file for each of the plurality of programs.

16. One or more non-transitory computer-readable media having programming instructions that are executable by one or more processors of a computing device to perform acts, the acts comprising:

compiling a source code file of a plurality of source code files into a program, the program included in a Basic Input/Output System (BIOS) file;

generating a debugging file including debugging information for the program;

utilizing a one-way deterministic function to generate an obfuscated filename for the debugging file; and

including a link to the debugging file in the program, the link including the obfuscated filename.

17. The one or more non-transitory computer-readable media of claim 16, wherein the acts further comprise utilizing at least an original filename of the source code file or the program as an input into the one-way deterministic function to generate the obfuscated filename.

18. The one or more non-transitory computer-readable media of claim 17, wherein the acts further comprise utilizing a cryptographic salt as another input into the one-way deterministic function to generate the obfuscated filename.

19. The one or more non-transitory computer-readable media of claim 18, wherein the one-way deterministic function is a hash function.

20. The one or more non-transitory computer-readable media of claim 16, wherein the program is one of a plurality of programs included in the BIOS file, wherein the BIOS file includes links to a plurality of debugging files, one debugging file for each of the plurality of programs.