Software security protection method and equipment

Abstract

The invention discloses a software security protection method. The method includes the steps of searching for all export functions in dynamic link library files in software and establishing a table of export functions; checking whether names of the corresponding called export functions exist in the table of export functions or not; if yes, storing related parameters of a local method into the table of export functions; if not calling the local method, actuating a replacement step; adapting, namely generating dispatch code snippets and replacing codes, which call the local method, in executable files; and replacing, namely generating a unified export function and replacing the names of all export functions with the name of the unified export function, wherein the unified export function is used for jumping to an original export function. By the software security protection method and system, only the unified export function is exposed from an interface of the software, and the software is more difficult to decompile and debug and is safer.

Description

technical field [0001] The invention relates to the technical field of computer and communication, in particular to a method and device for protecting software safety, which strengthens the safety protection of the interface between executable files and local dynamic link library files, and prevents them from being destroyed. Background technique [0002] A lot of Java software includes some executable programs (such as .jar, .war or .class format files) and local dynamic link library files (such as .dll or .so format files). When the software is running, the executable program calls the export interface in the dynamic link library to perform functions that can only be realized by native code. Due to the dynamic link between them, the export interface is realized through the mechanism related to the function name and function prototype (signature). Each export function has a corresponding local (native) method. In java software, the executable program Call the corresponding...

AI Technical Summary

Problems solved by technology

[0003] Since the export interface between the executable program of java software and the dynamic link library is realized by function name and function prototype, the information exposed by these export interfaces is likely to be used by crackers to detect and discover the logic and flow of the software , thereby damaging the software

However, the current code protection mainly simply protects the executable program of java software, or simply protects the local code in the dynamic link library, and lacks protection for the interface between them.

Images