JP5152640B2 - Software management system - Google Patents

Description

  The present invention relates to a software management system for packaged software, and more particularly, to a software management system capable of making detailed settings for various types of license conditions and detecting falsification of license information.

Generally, packaged software is manufactured by a software manufacturer and sold to users. At this time, there is a case where a license key is attached together with the package software in order to make it impossible to use the software even if an unauthorized person obtains the package software illegally.

In addition, when the software version is upgraded or the option is additionally purchased, it is necessary to add / update the license key information. Documents describing prior art that can prevent such unauthorized use of software include the following.

JP 2004-13743 A

Hereinafter, a conventional software management system will be described with reference to FIG. The software maker PC 10 is provided with a CPU, a storage unit, and the like (not shown), and license writing software 13 is installed in the storage unit. Here, the license writing software 13 is software for writing the license information 11 to the license key 12, and is owned only by the software manufacturer. The license key 12 is a portable storage medium, and is protected by, for example, a password, so that the user cannot freely read and write. The package software 14 is stored in a medium such as a CD ROM and sold to the user.

  Next, a procedure required until the user uses the package software 14 will be described. The software manufacturer uses the software manufacturer PC 10 to create license information corresponding to the software purchased by the user and its optional configuration. For example, this is a case where the main “Japanese-English translation software” is sold by combining an electrical / mechanical “technical term dictionary” as an option.

Next, the software manufacturer uses the software manufacturer PC 10 to write the license information 11 indicating that the package software 14 to be sold to the user is such a combination into the license key 12 using the license writing software 13. Then, the package software 14 and the license key 12 are shipped to the user.

The user who has obtained these installs the package software 14 on the user PC 20. Also, the user attaches a license key to the user PC 20 using, for example, a USB (Universal Serial Bus) port. The user activates the package software 14 installed on the user PC 20. The activated package software 14 reads the license information stored in the license key 12 and performs an operation corresponding thereto.

As described above, the conventional software management system ships the license key 12 storing the license information 11 together with the package software 22 to the user in order to prevent unauthorized use by a person who does not have use authority.

  However, the conventional technique described in FIG. 5 has the following problems. First, there is a problem with the storage capacity of the license key 12. The license key 12 is stored in special hardware in order to protect the stored contents. Therefore, unlike a general USB memory or the like, the storage capacity is small and expensive. In addition, if the option configuration is complicated, it cannot be recorded due to a capacity problem.

  Secondly, there is a problem of updating the license key 12. When the user upgrades the software or purchases additional options, the license information 11 needs to be added or updated at the same time. However, conventionally, the license information 11 has been updated by one of the following methods, but all have some problems.

First, there is a method in which the license information 11 is stored in a new license key 12 and shipped. However, since the license key 12 is expensive as described above, there is a problem in cost. In addition, when a new license key 12 is shipped, there are a total of two pieces of license information 11 together with the license key that has been used conventionally. Although it is different between old and new, the package software 14 can be used simultaneously by two user PCs 20.

As another method, there is a method in which the license key 12 shipped to the user is once returned to the manufacturer, and the license key 12 corresponding to the new option is written and retransmitted by the manufacturer. However, the transportation cost of the license key 12 is required, and the user cannot use the package software 14 for at least several days.

Further, as another method, there is a method of shipping the package software 14 in which the new license information 11 is written by CD ROM or the like. In this case, since an expensive license key 12 is not required, there is no cost problem. However, storing and shipping the license key 12 in the package software 14 without using special hardware capable of protecting the stored contents simultaneously falsifies the license information 11 and creates a risk of unauthorized use. Means that.

  The present invention has been made in view of these problems, and it is an object of the present invention to provide a software management system capable of making detailed settings for various types of license conditions and detecting falsification of license information. To do.

In order to achieve such a problem, the invention according to claim 1
In a software management system comprising a software manufacturer PC that generates packaged software and a user PC that installs and uses packaged software generated by the software manufacturer PC,
A license key number written in the software maker PC, and a license key that is checked when the license key number is attached to the user PC;
A license writing unit that attaches the license key to the software maker PC and writes a license key number to the license key;
A license file generated by creating an electronic signature based on license information based on at least one of the version, option, data amount, and usage restriction of the package software using a secret key at the software manufacturer PC; ,
A private key corresponding to the public key embedded in the packaged software;
With
The package software is installed on the user PC, the license file incorporated in a specific location of the package software is read, the electronic signature of the license information is read from the read license file , and the read electronic signature is installed And verifying with the public key embedded in the packaged software .

  The present invention has the following effects. Since an electronic signature using a public key cryptosystem is used, it is possible to prevent falsification of license information.

Hereinafter, the software management system of the present invention will be described. First, an outline of a mechanism for preventing falsification of license information according to the present invention will be described. The present invention uses a digital signature using a public key cryptosystem. Therefore, a signature scheme to be used first (for example, RSA (Rivest, Shamir, Adeleman) signature, DSA (Digital Signature Algorithm) signature, etc.) is determined, and a set of a public key and a private key is generated. The generated private key is strictly managed by the software manufacturer PC 100 so as not to be leaked to the outside, and the public key 222 is embedded in the source code of the package software 221 to be distributed.

Next, the configuration of FIG. 1 will be described. The software manufacturer PC 100 includes a CPU 110 and a storage unit 120. The CPU 110 operates license writing software (license writing means) 121 and license file generation software (license file generation means) 122 described later.

In addition to the license writing software 121 and the license file generation software 122 installed in the storage unit 120, a secret key 124 is installed. Here, the license writing software 121 writes the license key number into the license key 130.

Further, the license information XML 123 is shipped to the user as a part of the license file 126 later, and the license information such as the corresponding license key number and the information of the software option licensed to the user is stored. It is memorized, has excellent expressive ability, and can be used to restrict various types of licenses.

Next, a method for generating a license file will be described with reference to FIG. FIG. 2 is a flowchart of a license file creation method. First, the software manufacturer uses the software manufacturer PC 100 to create package information 221 purchased by the user and license information corresponding to the optional configuration in XML format. That is, the license information XML 123 is created.

The license file generation software 122 reads the license information XML 123 based on an instruction from the CPU 110, generates an electronic signature 125 as follows, and generates a license file 126 with the electronic signature 125 attached.

As a specific procedure, the CPU 110 reads the secret key 124 corresponding to the public key 222 embedded in the package software 221 stored in a medium such as CD ROM (SA1 in FIG. 2). Subsequently, the CPU 110 reads the license information XML 123 (SA2). Then, the CPU 110 generates the electronic signature 125 of the license information XML 123 using the private key 124 (SA3).

The electronic book name 125 is output to the license file 126 in accordance with an instruction from the CPU 110 (SA4). The CPU 110 also outputs the license information XML 123 to the license file 126 (SA5). That is, the license file 126 mainly stores the contents of the license information XML 123, but when shipped, an electronic signature 125 is attached to the license file 126 to prevent tampering.

Next, a license verification method will be described. FIG. 3 is a flowchart of the license verification method. The package software 221 shipped to the user is installed in the user PC 200, and calls the following processing when starting up or executing a specific function, and acquires license information created in an XML file. Then, based on the acquired information, it is determined whether activation / function execution is possible, and if an appropriate license can be confirmed, it is executed.

First, the CPU 210 of the user PC 200 reads the license file 223 incorporated in a specific location of the package software 211 (SB1). The CPU 210 reads the license information XML 123 together with the electronic signature 125 from the license file 223 (SB2, SB3).

The CPU 210 verifies the electronic signature 125 of the license information XML 123 with the public key 222 embedded in the package software 221 (SB4). If the verification is successful, the CPU 210 returns the license information to the calling package software 221 (SB5). However, if an error occurs such that the license file 223 cannot be read in any of the processes described above, it is determined that there is no appropriate license (SB6).

As described above, since the electronic signature using the public key cryptosystem is used, it is possible to discover the falsification of the license file 223 and to prevent unauthorized use of the software by a person without usage authority. That is, in order to successfully verify the electronic signature, it is necessary to sign with the private key 124 corresponding to the public key 223 embedded in the software. Also, due to the characteristics of the public key cryptosystem, it is extremely difficult to guess the secret key from the public key. Therefore, unless the private key 124 is leaked or the public key 222 embedded in the package software 221 cannot be altered, unauthorized use by falsification of the license file 223 is extremely difficult.

  In addition, because XML is used to describe license information, it is possible to easily cope with changes in the product system. In other words, with the conventional method, the capacity of the license key is limited, so information cannot be made redundant. Therefore, when the types of options increase or the product system changes, The format had to be changed significantly. On the other hand, since XML is used in the present invention, a new option can be added without greatly changing the existing description method (that is, before the change of the product system occurs).

In addition, because XML is used to describe license information, the expression capability is greatly improved, and fine restrictions can be imposed on many types of licenses. Therefore, for example, version restriction for each option, restriction on the expiration date, and quantity such as data amount can be restricted.

  Further, as in the prior art, since the license key 230 made of special hardware capable of protecting the stored contents is used, unauthorized copying can be prevented. That is, even if the license file 223 and the package software 221 are copied, the software will not operate unless there is a corresponding license key 230. Further, since the license key 230 is dedicated hardware, it is difficult to forge. Therefore, unauthorized use by copying the license file 223 cannot be performed unless the license key 230 is counterfeited or software is illegally altered.

  In addition, as in the past, it is easy to update the license. When the license is additionally purchased or upgraded, the license file 223 may be sent to the user by any method (e-mail, CD-R mail, etc.) and copied to a predetermined location on the user PC 200.

Next, application examples of the present invention will be described. By using the signature function of the program installed in the OS such as Microsoft Windows (registered trademark) and using the electronic signature for the software, the risk of unauthorized use due to modification of the public key in the program can be reduced. . Also, the risk of unauthorized use due to guessing of the secret key can be reduced by changing the combination of the secret key / public key every time the version is upgraded.

Next, an application example of the present invention will be described with reference to FIG. The software manufacturer makes the license management server 300 public and automates the distribution of the updated license. That is, the license registration tool 410 of the user PC 400 reads a number from the license key 430 and transmits it to the license management server 300 based on a command from a CPU (not shown).

The license management server 300 creates a license file 340 from the corresponding license information 310 based on a command from a CPU (not shown), and sends it back to the license registration tool of the user PC 410 via the network. The license registration tool 410 stores the license file 340 in a predetermined location.

In this way, sending the license file 340 via the network eliminates the need for mailing a CD-R or the like.

It is a block diagram of the software management system of this invention. It is a flowchart of the creation method of a license file. It is a flowchart of the verification method of a license. It is a block diagram of the application example of this invention. It is a block diagram of the conventional software management system.

Explanation of symbols

100 Software manufacturer PC
110 CPU
120 Storage Unit 121 License Writing Software 122 License File Generation Software 123 License Information XML
124 Private key 125 Electronic signature 126 License file 130 License key 200 User PC
210 CPU
220 Storage Unit 221 Package Software 222 Public Key 223 License File 230 License Key 300 License Management Server 310 License Information 320 License Management Server Software 330 License File Generation Software 340 License File 400 User PC
410 License registration tool 420 License file 430 License key

Claims (1)

In a software management system comprising a software manufacturer PC that generates packaged software and a user PC that installs and uses packaged software generated by the software manufacturer PC,
A license key number written in the software maker PC, and a license key that is checked when the license key number is attached to the user PC;
A license writing unit that attaches the license key to the software maker PC and writes a license key number to the license key;
A license file generated by creating an electronic signature based on license information based on at least one of the version, option, data amount, and usage restriction of the package software using a secret key at the software manufacturer PC; ,
A private key corresponding to the public key embedded in the packaged software;
With
The package software is installed on the user PC, the license file incorporated in a specific location of the package software is read, the electronic signature of the license information is read from the read license file , and the read electronic signature is installed A software management system characterized by verifying with a public key embedded in the packaged software .

Images