JP2003050640A - Method for preventing copy of software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent the copy of software by providing software capable of operating only by specific hardware (equipment). SOLUTION: At the time of preparing an execution file, at least a position designation pattern and a copyright pattern are embedded. This file is encoded, and installed in hardware in the following procedure. The encoded file is decoded, and the specific information of hardware is acquired, and an execution validity/invalidity pattern is generated by using the information and the copyright pattern. The execution validity/invalidity pattern is embedded at a prescribed position indicated by a position designation pattern so that the execution file can be finished. The execution file generates the execution validity/invalidity pattern from the specific information of the hardware and the copyright pattern. Then, this execution validity/invalidity pattern is compared with the execution validity/invalidity pattern embedded in the execution file itself so that the execution validity/invalidity can be judged.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to creation and execution of software that operates on a computer, and more particularly to software that has an effect of suppressing duplication of software.

[0002]

2. Description of the Related Art As the performance of computers has improved, various measuring instruments and other systems have been developed based on general computers such as personal computers. In many cases, software plays an important role in the operation of those devices. Since the software is digital data, it is generally easily duplicated. Therefore, it becomes possible to realize a device having the same performance by procuring hardware having the same configuration as that of a certain device and incorporating the copied software therein. Therefore, the sales side needs a function to prevent the user from easily copying.

As a countermeasure against this, a method of distributing software together with a predetermined keyword and inputting this keyword at the time of installation or operation so that the software can be used without restricting the function is generally used.

[0004]

However, in this method, the keywords are only stored in the hard disk, the memory, etc., and all of them are copied to other hardware, so that the copied software can be easily executed. Is possible. In the case of products such as measuring instruments that have a set of hardware and software, it is desirable that they are installed one-to-one. In other words, it is necessary not to operate even if the duplicated software is installed in the device having the same configuration.

In view of the above problems, the present invention has an object to suppress duplication of software by providing software that operates only on specific hardware (device).

[0006]

[Means for Solving the Problems] When creating an execution file (hereinafter referred to as an original execution file) obtained as a result of compiling a software source file, at least a position specification pattern and a work pattern are embedded, and a bit is calculated by a predetermined operation. Convert and encode the array.

The encoded file is returned to the original execution file by the inverse operation described above, the device information is acquired, and
By executing a predetermined calculation using the device information and the work pattern, an executability pattern is generated, and an execution file is generated by embedding the executability pattern in a predetermined position indicated by the position designation pattern.

The execution file acquires the unique information of the device, performs a predetermined calculation with the copyright pattern, generates an execution permission pattern, and compares it with the execution permission pattern embedded in the execution file itself to determine the execution permission. to decide.

[0009]

BEST MODE FOR CARRYING OUT THE INVENTION A first invention of the present invention is to provide a position designation pattern for designating at least an embedding position of an execution permission pattern indicating execution propriety of the execution file in an execution file of software, or a predetermined work. A software duplication prevention method characterized by embedding one of the patterns and converting the bit array of the execution file by a predetermined operation. By making the execution file an unexecutable file, a duplication suppression effect can be obtained. .

A second aspect of the present invention is a device for restoring a bit array of an execution file generated by the software duplication prevention method of the first aspect to an original bit array by a predetermined inverse operation and installing the execution file. Of the device information and a predetermined copyright pattern embedded in the device information and the execution file to generate an executability pattern indicating executability of the execution file, and embedding the executability pattern in the executability pattern. This is a software duplication prevention method characterized by embedding in accordance with a position designation pattern indicating a position, and a duplication suppression effect can be obtained by making the file executable only by a specific device.

According to a third aspect of the present invention, device information of a device in which an execution file of software is installed is acquired, and a calculation result of the device information and a predetermined pattern embedded in the execution file, A method for preventing software duplication, comprising comparing with an executability pattern indicating executability of the execution file embedded in the execution file, and determining that the software has been copied when the patterns do not match. Therefore, even if the software is copied, it is possible to detect from which device the software is copied.

In a fourth aspect of the present invention, the file name of the execution file is acquired from the device in which the execution file of software is installed, and the acquired file name and the execution file embedded in the execution file are acquired. This is a software duplication prevention method characterized by comparing file names and determining that the software has been duplicated when the file names do not match, and has an effect of inhibiting duplication by renaming files.

In the following description, it is assumed that development is performed using C language, but the present invention is not limited to this, and C ++ language, B
The ASIC language, assembler language, C # language, and other languages used to develop computer software have exactly the same effect.

Further, although a general computer (personal computer) will be described below, the present invention is not limited to this, and is similarly applicable to a device in which software operates, such as an embedded device, a game machine, or a home electric appliance.

(Embodiment 1) FIG. 1 is a schematic diagram showing a process of creating an execution file in the present invention. First, the encoding process will be described.

The source file 1 is a file created in C language, and includes the position designation pattern 11 and the writing pattern 1.
2 is defined therein. At least one of the position designation pattern and the work pattern is embedded. The original execution file 2 is a file obtained as a result of compiling the source file 1 with a C compiler, and the position designation pattern 21 and the work pattern 22 are embedded therein. Each of these corresponds to the result of compiling the position designation pattern 11 and the work pattern 12 defined in the source file 1. The intermediate execution file 3 is a file obtained by encoding the original execution file 2 with a predetermined conversion, and has the position specification pattern 31 inside.
And a work pattern 32 are embedded. Each of these corresponds to the result of encoding the position designation pattern 21 and the work pattern 32 in the original execution file 2. The above process is called the encoding process.

Here, the position designation pattern 21 and the work pattern 22 embedded in the original execution file 2 will be described. The position designation pattern 21 is for designating at which position the executability pattern to be embedded in the final executable file by the installer to be described later is embedded. The installer searches for the position designation pattern from the original execution file, and embeds the executability pattern at the position where the position designation pattern itself is embedded or at the position designated by the position designation pattern. The work pattern 22 is an arbitrary pattern defined in advance. The installer and the final executable file itself generate an executability pattern by performing a predetermined calculation using the copyright pattern and device information. The intermediate execution file 3 performs predetermined processing such as bit shift and logical operation on the original execution file 2,
The contents of the original execution file 2 including the position designation pattern 31 and the literary work pattern 32 are made unknown by a binary editor or the like.

Next, details of the encoding process will be described with a specific example. FIG. 2 is a flowchart showing the process of the encoding process. To facilitate understanding, the right side of the flowchart shows an outline of the memory contents in each process.

In step S201, the source file M
yApl. Read c into memory. MyApl. In c, as shown in the memory content 211, a #define statement is used to specify "MyPosition" as the position specification pattern.
n ”is defined and the work pattern is“ MySign ”.
Is defined. These patterns are examples, and may be arbitrary character strings, numeral strings, or bit strings as long as they are defined in advance. When the compilation is performed in step S202, the position designation pattern and the work pattern are incorporated as binary data, as shown in the memory contents 212. Note that the memory contents 212 are expressed in the same notation as in a general binary editor. The hexadecimal value part indicates the memory contents, and the part on the right side thereof is converted into a valid ASCII code. The same applies to other memory content displays. In step S203, the compilation result is used as the original execution file MyApl. Save as exe on the recording medium. Through the above processing, the source file MyA
pl. c to the original execution file MyApl. Get exe.

Note that the original execution file My has the function of determining whether or not it can be executed from the device information as in the fourth embodiment described later.
Appl. If exe has it, M is because the device information is not incorporated before it is installed in the device.
yAple. Even if exe is started, it does not operate normally and execution is stopped.

In step S204, step S203
The original execution file MyApl. Read exe into memory. The memory content 214 is equal to the memory content 212. In step S205, all the bits of the memory content 214 are left-shifted by 1 bit. The first bit shifts to the last bit. This operation is called encoding. This results in a memory content 215. Note that the encoding method described here is an example, and it is possible to define an encoding method by combining arbitrary bit shifts and logical operations. Also, compression or redundancy may be provided. In step S206, the encoding result is converted into the intermediate execution file MyApl. Save as enc on the recording medium.

By the above processing, the original execution file MyA
pl. exe to the intermediate execution file MyApl. enc
To get Intermediate execution file MyApl. The enc is just a binary file for the user. It is very difficult to analyze this file and obtain a valid executable file unless you know the conversion method in the encoding process. Therefore, the intermediate execution file AyApl. By storing the enc in the recording medium, a copy inhibition effect can be obtained.

In the above example, compilation and encoding are processed separately. Specifically, the processing is executed by two pieces of software, C compiler software and encoding software. These processes may be collectively performed by one software as shown in FIG. FIG. 3 is a flowchart showing a batch process of the encoding process. Here, steps S301, S302,
S303 and S304 correspond to step S20 of FIG. 2, respectively.
1, S202, S205, S206, and the memory contents 311, 312, 313 correspond to the memory contents 211, 212, 215 of FIG. 2, respectively. By doing so, the original execution file MyApl. exe
Is not saved on the recording medium. Original execution file M
yApl. As shown in the memory contents 212, since the position designation pattern and the work pattern can be specified from the binary data of the exe, a third party may analyze the contents, but the intermediate execution file MyApl. Since enc cannot determine where the position designation pattern or the work pattern is in the binary file and the analysis is difficult, it is possible to further enhance the copy inhibition effect.

If the sold device incorporates the installer created by the method of the present invention, the file can be installed only on the device. By distributing the intermediate execution file, the file can be installed only on the sold device, and cannot be installed on the device that the user independently procured. Therefore, copying of the execution file can be suppressed.

Alternatively, by grasping the unique information of the sold device in advance and distributing the execution file including the unique information when upgrading the version, a version effective only for the specific device can be obtained. It is possible to perform up.

(Embodiment 2) In this embodiment, description will be given of copy protection for a source file that does not have the position designation pattern and the work pattern in the first embodiment.

FIG. 4 is a flowchart showing a pattern addition type encoding process. In the first embodiment, the position specification pattern or the work pattern is embedded in the source file in advance. However, in the present embodiment, the source execution file obtained by compiling the source file having no such pattern does not contain these patterns. Shows how to embed a pattern. In FIG. 4, the process of compiling the source file to obtain the original execution file is omitted.

In step S401, the original execution file M
yApl. Read exe into memory. Memory contents 41
1 is an example of the memory contents at this time. Step S4
02, as shown in the memory content 412, step S
A position pattern is added to the end of the contents read in 401. Further, in step S403, the memory contents 41
As shown in 3, a work pattern is added to the end. In step S404, all bits of memory content 413 are left-shifted by 1 bit, and as a result, memory content 414 is obtained. The first bit shifts to the last bit. It should be noted that this encoding method is an example, and other methods may be used for encoding. In step S405, the memory contents 41
4 is an intermediate execution file MyApl. Save as enc on the recording medium.

As described above, it is possible to obtain the intermediate execution file having the same effect as that of the first embodiment.

(Embodiment 3) In this embodiment, a case will be described in which from which hardware the copied software is copied.

The decoding process in FIG. 1 will be described.

The intermediate execution file 3 is a file obtained in the encoding process described in the first embodiment, in which the position designation pattern 31 and the work pattern 32 are embedded. The original execution file 4 is a file obtained by decoding the intermediate execution file 3 by performing a predetermined conversion, and the position designation pattern 41 and the work pattern 42 are embedded therein. Original execution file 4 is original execution file 2
And the file is exactly the same. The execution file 5 is a file that is installed in the device in which this file is used, and includes an executability pattern 51 and a copyright pattern 52 generated from the device information of the device and the copyright pattern 42.
Is embedded. The above process is called a decoding process. However, the installation process is included.

Next, details of the decoding process will be described with a specific example. FIG. 5 is a flowchart showing the process of the decoding process. To facilitate understanding, the right side of the flowchart shows an outline of the memory contents in each process.

In step S501, the intermediate execution file MyApl. Read enc into memory. The intermediate execution file is obtained, for example, in the first embodiment, and the memory content 511 is the same as the memory content 215 of FIG. In step S502, all the bits of the memory content 511 are right-shifted by 1 bit. The last bit is shifted to the beginning. This operation is called decoding. This results in a memory content 512. This is the same as the memory content 212 or the memory content 214 in FIG. 2, and the original execution file MyA is stored in the memory.
pl. This means that exe has been restored. Note that the decoding method described here is an example, and if it is equivalent to the inverse operation of the operation performed at the time of encoding in the first embodiment, an arbitrary bit shift and logical operation are combined to define the decoding method. It is possible. As a result, the original execution file MyApl. It is sufficient if exe can be restored.

In step S503, the M of the network interface installed in the device to be installed is installed.
Acquires an AC (Media Access Control) address. MA
The C address is a unique number assigned to each network interface. MAC address 513
Is expressed in hexadecimal. The device information is not limited to the MAC, and may be unique device information held by the hardware to be installed. For example, the unique information held by the system or software including the OS, the product serial number, the disc ID number, or the like may be used.
In step S504, the M acquired in step S503
Using the AC address 513 and the copyrighted pattern “MySign” embedded in the memory content 512, an operation like operation 514 is performed to obtain an executability pattern. Note that the operation 514 is an example, and bit shift, logical operation, and other arbitrary operations may be defined.

In step S505, the memory contents 512
The executability pattern obtained in step S504 is overwritten and embedded in the position of the position designation pattern "MyPosition" of. This gives the memory content 515. In step S506, the memory contents 515 are stored in the execution file MyApl. Installation is performed by saving it as exe in the recording medium of the installation target device. At this time, an arbitrary time stamp may be given to the execution file. In addition, it is possible to limit the valid period by generating the executability pattern by using the date and time information.

By the above processing, the intermediate execution file My
Appl. Enc to execute the file MyApl. Get exe. Hardware specific information is executable file MyAp
l. It will be embedded in exe, and software and hardware will be a set. Therefore, even if only the software is copied, it is possible to detect from which hardware the copy is made.

(Embodiment 4) In this embodiment, a case will be described in which a duplicated executable file is detected and the operation of the effective file is stopped.

FIG. 6 is a flow chart showing the processing of the execution file. Hereinafter, the processing of the execution file will be described in detail with an example.

As shown in the memory contents 613, the execution file is embedded with the executability pattern by the method shown in the first and third embodiments. First, in step S601, when the execution file is activated, the device information of the hardware being executed is acquired. In this case, M
The AC address 611 is acquired. In step S602, calculation 6 is performed from the work pattern embedded in the execution file shown in the MAC address 611 and the memory content 613.
12 is performed and an executability pattern is internally generated. Calculation 612 is the same as calculation 514 used in the third embodiment. In step 603, the internally-executable executability pattern is compared with the executability pattern embedded in the execution file shown in the memory content 613. If they match, the operation continues normally. If they do not match, it means that the executable file is operating on hardware that is not included in the set. Therefore, it is determined that the executable file has been duplicated and the execution is stopped. At that time, a warning may be displayed to the user as in step 604.

As described above, the duplicated executable file can be detected and the operation of the executable file can be stopped. As a result, the copy suppression effect is further improved.

By applying the processing of the present embodiment to the original execution file, it becomes impossible to execute the original execution file without the installation as described in the first embodiment, and the effect is obtained. It will be an effective copy control.

(Embodiment 5) In this embodiment, description will be given of a case of preventing duplication by renaming.

By changing (renaming) the file name of the installed executable file, it is possible to operate as software different from that provided by the seller. In that case, it is difficult to find where the file is located on the computer (specifically, in the file system), especially when the number of files is large. In order to avoid this, it is desirable that the executable file cannot be executed when it is renamed.

FIG. 7 is a flowchart showing the rename prevention process.

When the execution file is started, the step S
In 701, the file name of the execution file itself is acquired. The file name is generally a file name registered in the file system of the device being executed. The execution file has the file name of the execution file itself embedded therein, and this file name is compared with the file name acquired in step S701 in step S702.
If they match, the operation continues normally. If they do not match, it is determined that the executable file has been renamed, that is, duplicated, and execution is stopped. At that time, a warning may be displayed to the user as in step 703.

Even if the software is not created by the method according to the first to fourth embodiments, it is possible to prevent the file duplication by the rename if the rename prevention function according to the present embodiment is incorporated. Is.

As described above, the copying of the execution file due to the change of the file name can be suppressed.

In the present invention, the respective embodiments have been described independently, but they may be combined and executed.

[0050]

As described above, according to the present invention,
In addition to making the original execution file unexecutable, it is possible to prevent a third party such as a user from analyzing the contents, and the effect of suppressing file duplication is obtained.

Further, even if only software is copied, it is possible to detect from which hardware the copy is made.

Further, the duplicated executable file can be detected and the operation of the executable file can be stopped.

Furthermore, it is possible to suppress the duplication by renaming.

[Brief description of drawings]

FIG. 1 is a schematic diagram showing a process of creating an execution file according to the first embodiment of the present invention.

FIG. 2 is a flowchart showing a process of the encoding process.

FIG. 3 is a flowchart showing batch processing of the encoding process.

FIG. 4 is a flowchart showing a pattern addition type encoding process according to the second embodiment of the present invention.

FIG. 5 is a flowchart showing a process of a decoding process according to the third embodiment of the present invention.

FIG. 6 is a flowchart showing processing of an executable file according to the fourth embodiment of the present invention.

FIG. 7 is a flowchart showing rename prevention processing according to the fifth embodiment of the present invention.

[Explanation of symbols]

1 source file 2, 4 original execution file 3 Intermediate execution file 5 executable files 11, 21, 31, 41, 51 Position designation pattern 12, 22, 32, 42, 52 Copyright patterns

Claims (4)

[Claims] 1. A bit of the execution file, wherein at least one of a position designating pattern for designating an embedding position of an executability pattern indicating the executability of the execution file or a predetermined work pattern is embedded in the execution file of the software. A method for preventing software duplication, which comprises converting an array by a predetermined operation. 2. The bit array of the execution file generated by the software duplication prevention method according to claim 1 is returned to the original bit array by a predetermined inverse operation, and device information of a device in which the execution file is installed is acquired, An executability pattern indicating executability of the execution file is generated from the device information and a predetermined work pattern embedded in the execution file, and the executability pattern is generated according to a position designation pattern indicating an embedded position of the executability pattern. A software copy prevention method characterized by embedding. 3. The device information of the device in which the execution file of the software is installed is acquired, and the calculation result of the device information and the predetermined pattern embedded in the execution file and the embedded result in the execution file. A method for preventing software duplication, comprising comparing an executability pattern indicating whether or not the execution file is present, and determining that the software has been duplicated when the patterns do not match. 4. The file name of the execution file is acquired from the device in which the execution file of the software is installed, and the acquired file name is compared with the file name of the execution file embedded in the execution file, A method of preventing software duplication, wherein the software is judged to have been duplicated when the file names do not match.