Anti-piracy encryption method for static library files in embedded system

Abstract

The invention proposes an anti-piracy encryption method for static library files in an embedded system. The method specifically comprises the following steps that the embedded system is started and connected with an encryption IC, and random numbers N1 and N2 are generated; a soft encryption program of the embedded system obtains the random numbers N1 and N2, and encrypts the other random number by taking any one random number as a key to generate an encryption result I; likewise, the encryption IC obtains the random numbers N1 and N2, executes the same encryption operation to generate an encryption result II, and feeds back the encryption result II to the embedded system; the embedded system compares the encryption result I obtained in the step S02 with the encryption result II, and if the encryption result I is consistent with the encryption result II, the system runs normally; and if the encryption result is inconsistent with the encryption result II, the system does not make a response. According to the method, the usage range of the library files is limited by adopting means of double authentication of random number encryption, hardware encryption IC and library file software encryption, so that the risk of decoding and embezzling the library files is greatly lowered.

Description

technical field [0001] The invention relates to an anti-piracy encryption method for static library files in an embedded system. Background technique [0002] In computer development, to implement a function, programmers must first write source code files (.c and .h files, the file language is a computer programming language and can be read) to control the computer and realize certain functions. After compiling with gcc (GNUCompiler Collection, a compilation suite supporting multiple programming languages), many object files (.o) will be obtained, which contain the implementation code of the program function (binary machine code, not capable of reading sex), and finally get the executable file after linking. [0003] In this process, in order to protect the code written by the creator, the object file (.o) file compiled by the gcc tool that needs to be packaged can be packaged into a static link library (.a file), so that only the .h index needs to be provided The header f...

AI Technical Summary

Problems solved by technology

However, this method only protects the ownership of the source code. If the other party is not interested in the implementation method, but only to obtain the implementation result for other purposes, then this protection method will inevitably be beyond its reach.

[0004] At present, there are very few methods for encrypting static library files. Most of the protection of source code is to provide header file indexes and .a static link library files (hereinafter referred to as providing static link libraries). Static link libraries are not only vulnerable to deciphering tools, but also cannot guarantee whether the library files are used within the legal scope

Images