JP3809495B1 - Software management system - Google Patents

Abstract

When distributing various kinds of software, for example, external leakage and unauthorized use of software including highly confidential information related to pre-market products are more reliably prevented by a simple method.
A distribution file set including an encrypted file and a dedicated installer created on a distribution source terminal is distributed to a distribution destination terminal using a recording medium and a network, and distributed on the distribution destination terminal. When installing the target software, the file access management server 30 performs double authentication of access authentication and installation authentication, and the distribution target software is distributed to a legitimate terminal (distribution destination terminal 20) of a legitimate user. Only installed and executed only at a legitimate user's legitimate terminal (distribution destination terminal 20).
[Selection] Figure 1

Description

  The present invention relates to a technique for managing software so that when distributing various software, the software is installed only on a legitimate user's terminal and executed only on the legitimate user's terminal.

  For example, when evaluating, inspecting, and checking a pre-commercial product (for example, a printer driver) and software accompanying the product, the software is stored in various recording media (flexible disk, CD, DVD, magnetic disk, optical disk, In the state recorded on the magneto-optical disk, etc., it is distributed to the person in charge (user) of the affiliated group company that performs the evaluation, inspection, and check, and installed on the terminal of the person in charge.

Since the software is related to a pre-market product, it naturally includes highly confidential information (external secret information) related to the product, and it is extremely undesirable for the software to leak to the outside.
However, under the present circumstances, the person in charge of the affiliated group company who has a confidentiality agreement and a confidentiality contract is trusted, and the software is recorded in a raw state and distributed without taking special measures such as encryption processing. There are many cases. Therefore, even if the user does not have malicious intent, there is a possibility that the recording medium is taken out of the company, and software on the recording medium is installed or copied, or an action that leads to leakage of confidential information is performed.

Thus, as a technique for preventing inadvertent leakage of information such as software provided by a recording medium or a network, for example, techniques disclosed in Patent Documents 1 and 2 below can be cited.
In Patent Document 1 below, when the medium is activated, the authentication key in the terminal is inquired by the browsing authentication software to determine whether or not the terminal can be used. If the authentication key is not installed in the terminal in advance, an unauthorized copy of the medium is created. But you can protect the browsing of the information you want. As a result, the terminals that can be browsed can be limited, and even if the password is leaked, the use of the copy can be protected.

Also, in Patent Document 2 below, the server encrypts the content using a predetermined key and distributes the encrypted data to the client, and the client stores the distributed encrypted data on the hard disk, and stores the encrypted data in the hard disk. Decoding is performed on a temporary memory area. That is, since the content is decrypted only by using the temporary memory area, it is necessary to create a memory area, and the content can be protected more strongly. Further, by restricting access to the memory area, external output of contents and the like are prevented, and leakage and unauthorized secondary use are prevented.
JP 2002-041363 A JP 2004-246431 A

However, in the technique disclosed in Patent Document 1, the user needs to install the authentication key provided by the authentication medium in advance on the terminal used for browsing, which is troublesome. If there is both an authentication medium and a recording medium holding information to be browsed, even an unauthorized user can view (install) information on the recording medium. There is a problem that unauthorized use cannot be reliably deterred.

  In the technique disclosed in Patent Document 2, content is protected by performing decryption processing in a temporary memory area and restricting access, but the content protection program is run on a terminal that has been distributed in advance. Any terminal can view the content. In other words, even users other than legitimate users (including users who use maliciously) can access (browse) the content and prevent unauthorized secondary use. However, there is a problem that information leakage due to browsing of content by users other than legitimate users cannot be reliably prevented.

  The present invention was devised in view of such problems, and when distributing various software, the software is installed only in a legitimate user's legitimate terminal, and only in a legitimate user's legitimate terminal. The purpose is to more reliably prevent external leakage and unauthorized use of software including highly confidential information (external secret information) related to pre-market products, etc., by a simple method. .

In order to achieve the above object, the software management system of the present invention (Claim 1) includes a distribution source terminal that creates a distribution file storing the distribution target software in order to distribute the distribution target software; The distribution file created by the distribution source terminal is distributed, and the distribution target software stored in the distribution file is to be installed, and the distribution source terminal distributes the distribution file to the distribution destination terminal. A file access management server that manages access to the distribution file, and the distribution source terminal converts a document file including information related to the distribution target software into a completed document file having a container function; Using the container function of the completed document file converted by the conversion means, the distribution to the completed document file An attachment means for attaching the software, and the completed document file to which the distribution target software is attached by the attachment means is encrypted with a predetermined encryption key managed by the file access management server. An encryption unit to be created; user information relating to a user who is permitted to access the encrypted file created by the encryption unit; access information permitted for the user and access information relating to an accessible period; Setting means for setting and notifying the file access management server, and a dedicated installer for causing the distribution destination terminal to install the encrypted file created by the encryption means and the distribution target software included in the encrypted file To create a distribution file set including The distribution destination terminal notifies the file access management server of access authentication information prior to accessing the encrypted file of the distribution file set distributed from the distribution source terminal, An access authentication requesting means for requesting access authentication as to whether or not the user of the distribution destination terminal is an authorized user permitted to access the encrypted file; and in response to an access authentication request by the access authentication requesting means When receiving a notification from the file access management server to authenticate that the user of the distribution destination terminal is an authorized user, the encrypted file is decrypted into the original completed document file, and the encrypted file is stored in the encrypted file. Decryption means for enabling access in accordance with the access information set for the access information, and decryption of the encrypted file by the decryption means Whether or not the user of the distribution destination terminal is authorized to install the distribution target software by notifying the file access management server of the installation authentication information by executing the dedicated installer later Installation authentication request means for requesting installation authentication as to whether or not the distribution destination terminal is a regular terminal to which the distribution target software is to be installed, and the file access management server in response to the installation authentication request by the installation authentication request means The distribution target software is extracted from the original completed document file when the user of the distribution destination terminal is notified that the user of the distribution destination terminal is an authorized user and the distribution destination terminal is authenticated. The distribution means and the distribution target software extracted by the extraction means are distributed. Processing means functioning as installation means for installing in the terminal, and the file access management server is set based on the user information and the access information set and notified by the setting means of the distribution source terminal A management means for managing the user's access to the encrypted file and the software to be distributed; and when the access authentication request is received from the distribution destination terminal, the distribution destination terminal based on the access authentication information And authenticating whether or not the user is an authorized user, and receiving the installation authentication request from the distribution destination terminal and an access authentication means for notifying the distribution destination terminal of the authentication result, Based on the information, whether or not the user of the distribution destination terminal is a regular user and the distribution destination terminal installs the distribution target software. Authenticates whether the authorized terminal to be tall, and the authentication result and characterized by being configured to include the installation authentication means for notifying the distribution destination terminal.

In such a software management system, the installation authentication means of the file access management server confirms that the distribution destination terminal that made the access authentication request and the distribution destination terminal that made the installation authentication request are the same. It may be one of the installation authentication conditions (Claim 2), or may be one of the installation authentication conditions that the distribution destination terminal that has made the installation authentication request is a specific terminal (Claim 3). One of the installation authentication conditions may be that the global IP (Internet Protocol) address of the distribution destination terminal that has made the installation authentication request is a predetermined address.

  In addition, while the distribution destination terminal prohibits access to the distribution target software from the original completed document file decrypted by the decryption means, the distribution destination terminal responds to the installation authentication request by the installation authentication request means. When receiving from the file access management server that the user of the distribution destination terminal is an authorized user and authenticating that the distribution destination terminal is a regular terminal, the file from the original completed document file It may be configured with permission / rejection means for permitting access to the distribution target software (claim 5).

Note that the distribution file set created by the creation means of the distribution source terminal may be distributed to the distribution destination terminal via a network (Claim 6) or recorded in a recording medium. It may be distributed to the distribution destination terminal (claim 7).
Further, the file access management server may comprise log recording means for collecting and recording the installation operation log of the distribution target software at the distribution destination terminal (claim 8). At that time, the file access management server refers to the installation operation log collected by the log recording means, and for the distribution destination terminal that has successfully installed the distribution target software, It may be configured to include an install operation restricting unit that prohibits an install operation of software (Claim 9), and further, the distribution is performed after the file access management server prohibits the install operation by the install operation restricting unit. Even if it is configured to temporarily cancel the prohibited state of the installation operation by the installation operation restricting means in response to an instruction from the administrator when there is a request for reinstallation of the distribution target software from the destination terminal Good (claim 10).

In the software management system as described above, the distribution target software is related to a product released at a predetermined date and time, and the setting unit of the distribution source terminal can access the data until the predetermined date and time. You may set as a period (Claim 11).
On the other hand, the distribution target software is distributed to a plurality of distribution destination terminals and is subjected to operation evaluation by each distribution destination terminal. The management means of the file access management server receives the evaluation from all the distribution destination terminals. Collecting evaluation results of distribution target software, and according to the collected evaluation results, the encrypted files and distribution target software by all the distribution destination terminals set by the setting unit of the distribution source terminal It may be configured to change the access authority or the accessible period for (Claim 12).

  At that time, the distribution target software is related to a product that is released on a predetermined date and time, and the management means of the file access management server has improved the evaluation results from all the distribution destination terminals. In this case, the access period for the encrypted file and the software to be distributed by all the distribution destination terminals may be changed by the predetermined date and time (Claim 13). The access authority for the encrypted file and the software to be distributed by all the distribution destination terminals may be changed so that all types of access can be made (claim 14).

  Further, the distribution target software relates to a product released after the evaluation by the plurality of distribution destination terminals is completed, and the management means of the file access management server determines the evaluation results from all the distribution destination terminals. The release date of the product is determined, and the access period for the encrypted file and the distribution target software by all the distribution destination terminals is changed to the determined release date. (Claim 15) The access authority for the encrypted file and the distribution target software by all the distribution destination terminals may be changed to be accessible to all types at the determined release date and time. (Claim 16).

  Furthermore, when the management means of the file access management server gives a good evaluation result from all the distribution destination terminals, the access to the encrypted file and the distribution target software by all the distribution destination terminals. The authority or the accessible period may be changed to all types of inaccessible (claim 17).

  According to the present invention described above, the distribution file set including the encrypted file and the dedicated installer created at the distribution source terminal is distributed to the distribution destination terminal using the recording medium or the network. When the distribution destination terminal receives a notification from the file access management server to authenticate that the user of the distribution destination terminal is an authorized user in response to the access authentication request, the encrypted file in the distribution file set is Decrypted into the original completed document file. The user of the distribution destination terminal can only access the decrypted original completed document file according to the access information (access authority and accessible period) set in the distribution source terminal. At the time of this decryption, access to the distribution target software from the decrypted original completed document file is prohibited, and the user of the distribution destination terminal takes out the distribution target software immediately after decryption. I can't do that. After this, when the user of the distribution destination terminal refers to the information related to the distribution target software in the completed document file, the dedicated installer in the distribution file set is executed to install the distribution target software on the distribution destination terminal. First, an installation authentication request is made from the distribution destination terminal to the file access management server. In response to the installation authentication request, when the file access management server receives a notification that the user of the distribution destination terminal is an authorized user and that the distribution destination terminal is an authorized terminal, the above-mentioned retrieval access is permitted. Then, the distribution target software is extracted from the restored original completed document file, and the distribution target software is installed in the distribution destination terminal.

As a result, when distributing software to be distributed, double authentication of access authentication and installation authentication is performed, and the software to be distributed is installed only on the authorized terminal (distribution destination terminal) of the authorized user. In addition to being executed only at a legitimate user's legitimate terminal (distribution destination terminal), the distribution target software is installed only by a dedicated installer in the distribution file set. ) And the software that accompanies it, such as distributing the software to the evaluator (user) and installing it on the evaluator's terminal (distribution destination terminal) Easy external leakage and unauthorized use of software containing highly confidential information (external secret information) By law, it can be more reliably prevented.

  At the time of installation authentication, in addition to the authentication of authorized users and authorized terminals as described above, the distribution destination terminal that made the access authentication request is the same as the distribution destination terminal that made the installation authentication request, and the installation authentication By making the installation authentication condition that the distribution destination terminal that made the request is a specific terminal and that the global IP address of the distribution destination terminal that made the installation authentication request is a predetermined address, The installation authentication condition of the distribution destination terminal to be installed is set more severely, and external leakage and unauthorized use of the distribution target software can be prevented more reliably. Here, by setting the global IP address as the installation authentication condition, the distribution target software can be installed in the distribution destination terminal when the distribution destination terminal exists at a predetermined position specified by the global IP address.

  In addition, the file access management server collects and records the installation operation log of the distribution target software at the distribution destination terminal, thereby recording when and on which terminal the distribution target software was installed. Thus, when any unauthorized use or unauthorized installation is detected for the distribution target software, it is possible to analyze the unauthorized use or unauthorized installation based on the installation operation log.

  At that time, the file access management server refers to the installation operation log, and for the distribution destination terminal that successfully installed the distribution target software, the subsequent distribution target software installation operation (or distribution target from the completed document file) By configuring the software access to be prohibited, it is possible to prevent installation of the distribution target software over and over, and more reliably prevent external leakage and unauthorized use of the distribution target software. it can.

  However, if the file access management server requests the reinstallation of the distribution target software from the distribution destination terminal after prohibiting the installation operation as described above, the installation operation (or completed document) is requested according to the administrator's instruction. It is necessary to reinstall the installed distribution target software due to some troubles, etc. by temporarily canceling the prohibition status of the distribution target software (access from the file). If it occurs, it can be reinstalled under the approval of the administrator, so that convenience at the distribution destination terminal is not impaired.

  Further, in the software management system as described above, when the distribution target software is related to a product released at a predetermined date and time, the distribution source terminal sets up to the predetermined date and time as an accessible period. Thus, for example, as described above, in order to evaluate a pre-commercial product and its accompanying software, the software is distributed to an evaluator (user) and the evaluator's terminal (distribution destination terminal) In the case of installation, the software and the encrypted file can be accessed for evaluation until the predetermined date and time, and the software and the encrypted file are automatically accessed when the predetermined date and time are reached. It becomes impossible to prevent unauthorized use of software related to commercially available products.

On the other hand, when the distribution target software is distributed to a plurality of distribution destination terminals and is subjected to an operation evaluation by each distribution destination terminal, the file access management server displays the evaluation results of the distribution target software from all distribution destination terminals. Collected files and distribution of encrypted files and distributions by all distribution destination terminals by changing the access authority or access period for the encrypted files and distribution target software by all distribution destination terminals according to the collected evaluation results It becomes possible to manage access to the target software.

  For example, if the distribution target software is related to a product released at a predetermined date and time, and the evaluation results from all the distribution destination terminals are good, the encrypted files by all the distribution destination terminals By changing the access period for the software to be distributed by the predetermined date and time, the software and encrypted files are automatically disabled when the predetermined date and time are reached. Unauthorized use of such software can be prevented more reliably. On the other hand, if it is determined that there is no need to maintain confidentiality for software at the same time as the release, all types of access to encrypted files and distribution target software by all distribution destination terminals at the predetermined date and time are given. By changing the setting so that it is possible, access to the software and the encrypted file can be automatically made free at a predetermined date and time.

  In addition, when the distribution target software is related to a product that is released after evaluation is completed by multiple distribution destination terminals, and the evaluation results from all distribution destination terminals are good, the product release date and time By changing the access period for the encrypted files and distribution target software by all distribution destination terminals to the determined release date and time, the software and encryption are automatically set when the release date and time are reached. Access to the file becomes impossible, and unauthorized use of software related to a commercially available product can be prevented more reliably. On the other hand, if there is no need to maintain confidentiality for the software at the same time as the release, all types of access rights to the encrypted files and distribution target software by all distribution destination terminals are determined at the determined release date and time. By changing the setting so that it can be accessed, it is possible to automatically make the access to the software and the encrypted file free when the date of publication is reached. In this case, since the release date and time can be determined at the time when the evaluation of all the evaluators is completed, the release date and time can be set earlier when the operation evaluation is completed earlier.

  Furthermore, when the evaluation results from all the distribution destination terminals are good, the access authority or the access period for the encrypted files and distribution target software by all distribution destination terminals is changed to disable access to all types. By doing so, access to the software or encrypted file automatically becomes impossible at that time, and unauthorized use of software related to a commercially available product can be prevented more reliably.

Embodiments of the present invention will be described below with reference to the drawings.
[1] Configuration of Software Management System of this Embodiment FIG. 1 is a block diagram showing the configuration of a software management system as an embodiment of the present invention. As shown in FIG. The hardware management system 1 connects at least one distribution source terminal 10, a plurality of distribution destination terminals 20, and a file access management server 30 via a network [for example, an in-house LAN (Local Area Network) or the Internet] 40. Are configured to be communicable with each other.

Note that the software management system 1 in the present embodiment uses the software as a distribution target software as an affiliated group company or the like in order to evaluate a pre-commercial product (for example, a printer driver) and software associated therewith. It shall be applied to prevent leakage when distributed to multiple evaluation personnel (users). That is, in the software management system 1 according to the present embodiment, as will be described later, the distribution source terminal 10 creates a distribution file set (described later) including the distribution target software, and the distribution file set has a plurality of evaluation personnel. The distribution target software in the distribution file set is installed in the terminals (distribution destination terminals) 20 of a plurality of evaluation personnel and becomes an evaluation target, and the file access management server 30 includes each evaluation personnel. The result of evaluation of the distribution target software performed at the terminal 20 is collected, and the access to the distribution target software or the like by the distribution destination terminal 20 is managed based on the collected result.

[1-1] Configuration of Distribution Source Terminal A distribution source terminal (client PC) 10 is a personal computer (PC) used by employees (users; software distributors; distributors) in a company or the like. Are connected to the distribution destination terminal 20 and the file access management server 30 via the network 40 so that they can communicate with each other.

  Then, in order to distribute the distribution target software, the distribution source terminal 10 creates a distribution file (distribution file set 50 to be described later) storing the distribution target software, and includes at least conversion means 11 and attachment means 12. , Functions as an encryption unit 13, a setting unit 14, and a creation unit 15. These functions are realized by a processing unit [CPU (Central Processin Unit)] constituting the distribution source terminal 10 executing a predetermined application program.

  The conversion unit 11 converts a document file including information related to the distribution target software into a completed document file having a container function [here, a PDF (Portable Document Format) file that is difficult to tamper with]. Here, the document file including the information related to the distribution target software is, for example, a user's manual / simplified manual of the distribution target software (a program such as a printer driver) or distribution information about the distribution target software. A detailed document is created in advance by a user or the like as a file. Note that conversion to a PDF file is performed by, for example, a PDF driver, and by starting the PDF driver, the document file is converted to PDF and a PDF file is generated.

The attachment unit 12 attaches and stores software to be distributed to the PDF file using the container function of the PDF file converted by the conversion unit 11.
The encryption unit 13 uses the predetermined encryption key (actually received from the file access management server 30) managed by the file access management server 30 for the PDF file to which the distribution target software is attached by the attachment unit 12. It encrypts and creates an encrypted file.

  The setting unit 14 includes user information related to a user (evaluator) who permits access to the encrypted file created by the encryption unit 13 (that is, installation of distribution target software), and the user. Access information regarding permitted access authority and accessible period is set and notified to the file access management server 30.

  The setting by the setting means 14 is performed before the encryption operation or in parallel with the encryption operation. For a user who accesses the encrypted file, an access authority to the encrypted file (for example, a document file) (Browsing, commenting, printing, copying, and authority to execute the selected access from among various accesses such as retrieving the distribution target software stored by the container function). It is assumed that it is performed on the management server 30 (authority table).

Here, at least the document file browsing authority is set as the access authority. However, the authority to extract the distribution target software is not set, that is, the distribution destination terminal 20 is initially set so that the distribution target file cannot be extracted. As for the right to retrieve the distribution target software, permission means 26 (described later) of the distribution destination terminal 20 is used.
Is switched as described later. In addition, when the distribution target software is related to a product released on a predetermined date and time, the setting unit 14 may set the period until the predetermined date and time as an accessible period.

  The creation unit 15 includes a plug-in 51 that is executed to access the file access management server 30 when the encrypted file is decrypted and accessed (viewed) at the distribution destination terminal 20, and at least one created by the encryption unit 13. A distribution file set 50 including two encrypted files 52 and a dedicated installer 53 for installing the distribution target software included in the encrypted file 52 in the distribution destination terminal 20 is created as a distribution file. The distribution file set 50 created by the creating means 15 may be distributed to each distribution destination terminal 20 via the network 40 by e-mail or the like, or may be a recording medium 50A (for example, flexible disk, CD, DVD, magnetic). It may be distributed to each distribution destination terminal 20 in a state of being recorded on a disk, an optical disk, a magneto-optical disk, or the like.

The dedicated installer 53 is a dedicated installer for the distribution target software included in the same distribution file set 50, and the distribution target software is installed on the distribution destination terminal 20 only by the dedicated installer 53. ing.
Further, as will be described later, the dedicated installer 53 realizes a communication function with the file access management server 30 (function as installation authentication request means 23 described later).

Furthermore, as described later, a user who can access the encrypted file (a user who is permitted to decrypt the encrypted file, that is, a user who has been authenticated as an authorized user by access authentication described later) is activated. In addition, the dedicated installer 53 operates on the distribution destination terminal 20 only when the distribution destination terminal 20 that has started the dedicated installer 53 is authenticated as an authorized terminal by installation authentication described later. .
In this embodiment, the plug-in 51 is also attached to the distribution file set 50. However, if it is known in advance that the plug-in 51 is installed in each delivery destination terminal 20, the plug-in 51 is attached. May be omitted.
Detailed functions of the dedicated installer 53 will be described later.

[1-2] Configuration of Distribution Destination Terminal In this embodiment, the distribution destination terminal (client PC) 20 is a personal computer (PC) or the like used by an evaluation person (employee) in the related group company as described above. The information processing apparatus is connected to the distribution source terminal 10, another distribution destination terminal 20, and the file access management server 30 via the network 40 so that they can communicate with each other.

  The distribution destination terminal 20 is to distribute the distribution file set created by the distribution source terminal 10 and install the distribution target software stored in the distribution file set. 21, decryption means 22, installation authentication request means 23, take-out means 24, installation means 25, and permission / rejection means 26. These functions are realized by a processing unit (CPU) constituting the distribution destination terminal 20 executing a predetermined application program. In this embodiment, the functions as the installation authentication requesting unit 23, the extracting unit 24, the installing unit 25, and the permission / refusal unit 26 function as a distribution file set 50 (recording medium) after the decryption unit 22 decrypts the encrypted file 52. 50A) is realized by the processing unit being activated and executed by the processing unit.

The access authentication requesting means 21 sends the access authentication information (user identification information and password) to the file access management server 30 prior to accessing (browsing) the encrypted file 52 of the distribution file set 50 distributed from the distribution source terminal 10. The user of the distribution destination terminal 20 (the person in charge of evaluation) requests access authentication as to whether or not the authorized user is permitted to access the encrypted file 52.

Note that the user ID and password as access authentication information may be notified to the file access management server 30 via the plug-in as those registered in advance in the distribution destination terminal 20, or the user (evaluator) ) May be notified to the file access management server 30 via a plug-in.
When a plug-in for accessing the file access management server 30 is installed in advance in the distribution destination terminal 20, the plug-in is activated, whereas when the plug-in is not installed, The plug-in 51 is read from the distribution file set 50 (recording medium 50A) and installed in the distribution destination terminal 20, and then activated.

  In response to the access authentication request from the access authentication requesting unit 21, the decrypting unit 22 sends a notification from the file access management server 30 to authenticate that the user (evaluator) of the distribution destination terminal 20 is an authorized user. When received, the encrypted file 52 of the distribution file set 50 (recording medium 50A) is decrypted into the original PDF file, and the encrypted file 52 can be accessed according to the set access information. It is. Here, the document (instruction manual or the like) in the original PDF file is displayed on the display (not shown) of the distribution destination terminal 20, and the user (evaluator) can view it.

  The installation authentication request means 23 notifies the file access management server 30 of the installation authentication information through the plug-in, and the user (evaluator) of the distribution destination terminal 20 is an authorized user who is permitted to install the distribution target software. Whether or not the distribution destination terminal 20 is a legitimate terminal to which the distribution target software is to be installed is requested.

  As installation authentication information, in addition to user identification information and password, company identification information (information for specifying the related group company), server name, global IP (Internet Protocol) address, MAC (Medium Access Control) address , The host name and the like are notified, and those registered in advance in the distribution destination terminal 20 are notified to the file access management server 30 via the plug-in. At this time, the user ID and password as the installation authentication information may be the same as or different from the user ID and password as the access authentication information, and are registered in advance in the distribution destination terminal 20. Something may be notified to the file access management server 30 via the plug-in, or what the user (evaluator) inputs using the keyboard or the like is notified to the file access management server 30 via the plug-in. May be.

In response to the installation authentication request from the installation authentication requesting unit 23, the take-out unit 24 is that the user (evaluator) of the distribution destination terminal 20 from the file access management server 30 is a regular user and the distribution destination terminal 20 is a regular terminal. When receiving a notification to authenticate, the distribution target software is extracted from the original PDF file.
At this time, in this embodiment, the setting unit 14 of the distribution source terminal 10 is initially prohibited from accessing the software to be distributed, but the permission / rejection unit 26 uses the installation authentication request unit 23 to request an installation authentication. In response to a notification from the file access management server 30 that the user of the distribution destination terminal 20 (evaluator) is an authorized user and that the distribution destination terminal 20 is authenticated as a regular terminal. Access to the distribution target software from the PDF file is temporarily permitted.

The installation unit 25 designates the distribution target software extracted by the extraction unit 24 in a state in which the extraction access of the distribution target software is permitted by the permission / rejection unit 26 by the user (evaluator) at the distribution destination terminal 20. Installed in a folder (see FIG. 3).
One terminal may be provided with both the function as the distribution source terminal 10 and the function as the distribution destination terminal 20.

[1-3] Configuration of File Access Management Server The file access management server 30 is communicably connected to the distribution source terminal 10 and the distribution destination terminal 20 via the network 40, and distributed from the distribution source terminal 10 to the distribution destination terminal 20. It manages the access to the distributed file set (distribution file), and has functions as a management means 31, an access authentication means 32, an installation authentication means 33, a log recording means 34, and an installation operation restriction means 35. . These functions are realized when a processing unit (CPU) constituting the file access management server 30 executes a predetermined application program.

Here, the management unit 31 determines the encrypted file 52 and the distribution target based on the user information and the access information (information set in the authority table) set and notified by the setting unit 14 of the distribution source terminal 10. It manages the user's (evaluator) access to the software.
Further, the management means 31 collects the results of the operation evaluation of the distribution target software performed at the terminal 20 of each evaluation person, and accesses the distribution target software and the like by the distribution destination terminal 20 based on the collected result. It also fulfills the function of managing Specifically, the management unit 31 collects the operation evaluation results of the distribution target software from all the distribution destination terminals 20, and is set by the setting unit 14 of the distribution source terminal 10 according to the collected operation evaluation results. The access authority or the accessible period for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 is changed. More specifically, the management means 31 performs access management of any one of the following items (11) to (15), for example.

(11) When the distribution target software is related to a product released on a predetermined date and time, and all the distribution destination terminals 20 have answered “good (OK)” as the operation evaluation result In addition, the access period for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 is changed by the predetermined date and time.
(12) When the distribution target software is related to a product released on a predetermined date and time, and all the distribution destination terminals 20 have answered “good (OK)” as the operation evaluation result In addition, on the predetermined date and time, the access authority for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 is changed to be accessible to all types.

  (13) The distribution target software is related to a product that is released after the completion of evaluation by a plurality of distribution destination terminals 20, and the operation evaluation result from all distribution destination terminals 20 is “good (OK)”. When the answer to the above is received, the release date of the product is determined, and the access period for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 is changed to the determined release date.

(14) The distribution target software is related to a product released after the completion of evaluation by a plurality of distribution destination terminals 20, and the operation evaluation result from all distribution destination terminals 20 is “Good (OK)”. When the answer to the above is received, the release date of the product is determined, and the access authority for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 is determined for all types of access at the determined release date. Change the setting as possible.
(15) Access authority or access to the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 when all the distribution destination terminals 20 have answered “good” as the operation evaluation result. Change the possible period to all types of inaccessibility.

  When receiving an access authentication request from the distribution destination terminal 20, the access authentication means 32 authenticates whether or not the user (evaluator) of the distribution destination terminal 20 is a regular user based on the access authentication information. The authentication result is notified to the distribution destination terminal 20. In practice, the user identification information and password included in the access authentication information are stored in advance in the file access management server 30 as user identification information and By determining whether or not it matches the password, it is determined and authenticated whether or not the user (evaluator) is a regular user (authorized user).

  When receiving the installation authentication request from the distribution destination terminal 20, the installation authentication means 33 determines whether or not the user (evaluation person) of the distribution destination terminal 20 is a regular user based on the installation authentication information. The destination terminal 20 authenticates whether or not the distribution target software is to be installed, and notifies the distribution destination terminal 20 of the authentication result.

  Similar to the access authentication unit 32, the installation authentication unit 33 determines whether or not the user identification information and password included in the installation authentication information matches the user identification information and password registered and stored in the file access management server 30 in advance. In addition to determining / authenticating whether the user (evaluator) is a regular user (authorized user), installation authentication with the distribution destination terminal 20 that has requested access authentication The distribution destination terminal 20 that made the request is the same, the distribution destination terminal 20 that made the installation authentication request is a specific terminal, and the global IP address of the distribution destination terminal that made the installation authentication request is predetermined. Confirm that the address is correct and that the company identification information indicates a specific company. It may be used as one of the.

The log recording means 34 collects an installation operation log of software to be distributed at the distribution destination terminal 20 and records it in a database (not shown) or the like.
The installation operation restriction unit 35 refers to the installation operation log collected by the log recording unit 34, and for the distribution destination terminal 20 that has successfully installed the distribution target software, prohibits the subsequent installation operation of the distribution target software. To do. The function as the installation operation restriction unit 35 can also be realized by the management unit 31 described above. The file access management server 30 installs in response to an instruction from the administrator when there is a request for reinstallation of the distribution target software from the distribution destination terminal 20 after the installation operation restricting means 35 prohibits the installation operation. The prohibition state of the installation operation by the restricting means 35 is temporarily canceled.

[2] Operation of Software Management System of the Present Embodiment Next, the operation of the software management system 1 of the present embodiment configured as described above will be described with reference to FIGS.
[2-1] Operation of Distribution Source Terminal Operation of distribution source terminal 10 in software management system 1 of the present embodiment (distribution file) according to the flowchart (steps S11 to S18) shown in FIG. 4 with reference to FIG. The set creation operation) will be described. FIG. 2 is a schematic diagram for explaining the distribution file set creation operation in the software management system 1 (distribution source terminal 10) of the present embodiment.

In the distribution source terminal 10, firstly, distribution target software is created or prepared, and a user manual / simplified manual document file of the distribution target software (for example, a printer driver) is generated (step S 11). The document file is converted into a PDF file having a container function by the conversion means 11 (step S12; see arrow A11 in FIG. 2).

  Using the PDF file container function, the attachment means 12 attaches and stores software to be distributed to the PDF file (step S13; arrow A12 in FIG. 2), and then the user of the distribution source terminal 10 (the person in charge of distribution) The user) by the setting means 14, user information regarding the user (evaluator) who permits access to the PDF file (that is, installation of the distribution target software) and the access authority permitted to the user. And the access information regarding the accessible period are set, notified to the file access management server 30, and set in the authority table (step S14). In the present embodiment, as described above, at least the document file viewing authority is set as the access authority, the extraction of the distribution target software is prohibited, and the release date of the product related to the distribution target software is determined. In this case, the predetermined date and time is set as the accessible time limit.

  Thereafter, the PDF file to which the distribution target software is attached is encrypted by the encryption unit 13 with a predetermined encryption key managed by the file access management server 30, and an encrypted file 52 is created (step S15). ; See arrow A13 in FIG. 2). Then, the creation unit 15 creates a distribution file set 50 including the plug-in 51, the encrypted file 52, and the dedicated installer 53 (step S16; see arrow A14 in FIG. 2). In the present embodiment, for example, after being recorded on a recording medium 50A such as a CD (step S17; see arrow A14 in FIG. 2), the recording medium 50A is delivered to the evaluator (step S18). . As described above, the distribution file set 50 may be distributed to each distribution destination terminal 20 via the network 40 by e-mail or the like without being recorded in the recording medium 50A.

[2-2] Operation of Distribution Destination Terminal Next, with reference to FIG. 3, the operation of the distribution destination terminal 20 in the software management system 1 of this embodiment (steps S21 to S36) according to the flowchart shown in FIG. (Installation operation of distribution target software) will be described. FIG. 3 is a schematic diagram for explaining the installation operation of the distribution target software in the software management system 1 (distribution destination terminal 20) of the present embodiment.

  In each distribution destination terminal 20, when the recording medium 50A is inserted into the distribution destination terminal 20 in order to install the distribution target software from the recording medium 50A (distribution file set 50) distributed by the person in charge of distribution (step) First, it is determined whether or not the plug-in 51 has already been installed in the distribution destination terminal 20 (step S22). If not installed (NO route in step S22), the plug from the recording medium 50A is plugged. In 51 is installed (step S23; see arrow A21 in FIG. 3). When the plug-in 51 is installed (YES route in step S22), the process in step S23 is skipped.

Thereafter, when the plug-in 51 is activated and the user (evaluator) of the distribution destination terminal 20 designates the encrypted file 52, the access authentication request means 21 generates access authentication information (user identification information and password) as a file. The access management server 30 is notified, and access authentication is requested as to whether or not the user (evaluator) of the distribution destination terminal 20 is an authorized user permitted to access the encrypted file 52 (step S24). . When the response from the file access management server 30 in response to this access authentication request is a notification that the user (evaluator) of the distribution destination terminal 20 is not a regular user (NO route in step S25) ) An error notification is made at the distribution destination terminal 20 (step S26), and the process is terminated.

  On the other hand, when the response from the file access management server 30 is a notification to authenticate that the user (evaluator) of the distribution destination terminal 20 is a regular user (YES route in step S25), decryption is performed. The encrypting means 22 decrypts the encrypted file 52 of the distribution file set 50 (recording medium 50A) into the original PDF file (step S27), and the document (instruction manual etc.) in the PDF file is distributed to the distribution destination terminal 20. Are displayed on the display (not shown) and viewed by the user (evaluator) (step S28; see arrow A22 in FIG. 3). At this time, as described above, it is prohibited to extract the distribution target software from the PDF file.

  When the user (evaluator) who has viewed the document requests installation of the distribution target software (YES route in step S29), the dedicated installer 53 of the distribution file set 50 (recording medium 50A) is activated (step S29). S30; see arrow A23 in FIG. 3). When the dedicated installer 53 is activated, the user authentication information and password are requested by the installation authentication requesting means 23, and together with the user identification information and password input by the user (evaluator) in response to the request, The server name, global IP address, MAC address, host name, etc. described above are notified to the file access management server 30 as installation authentication information, and the user (evaluator) of the distribution destination terminal 20 permits installation of the distribution target software. Installation authentication is requested as to whether the distribution target terminal 20 is the authorized terminal where the distribution target software is to be installed (step S31).

  The response from the file access management server 30 in response to the installation authentication request is a notification that the user (evaluator) of the distribution destination terminal 20 is not a regular user, and the distribution destination terminal 20 is the distribution target If at least one of the notifications indicating that the software is not a legitimate terminal to be installed (NO route in step S32), an error notification is given in the distribution destination terminal 20 (step S33), and the process is terminated. .

  On the other hand, the response from the file access management server 30 is that the user (evaluator) of the distribution destination terminal 20 is an authorized user permitted to install the distribution target software and the distribution destination terminal 20 is the distribution target software. Is a notification to authenticate that it is a legitimate terminal to be installed (YES route in step S32), the permission / refusal means 26 from the PDF file designated / selected by the user (evaluator) The retrieval access of the distribution target software is temporarily permitted (step S34), the distribution target software is extracted from the PDF file by the extraction unit 24 (step S35), and is extracted by the extraction unit 24 by the installation unit 25. The distribution target software is a user (evaluation manager) at the distribution destination terminal 20. Is installed in the folder specified by user) (Step S36; refer to arrow A24 in Fig. 3).

[2-3] Operation of File Access Management Server Next, the operation of the file access management server 30 in the software management system 1 of the present embodiment will be described with reference to the flowchart (steps S41 to S60) shown in FIG.
When the file access management server 30 receives an access authentication request from the distribution destination terminal 20 (YES route in step S41), the access authentication means 32 uses the user (evaluation person) of the distribution destination terminal 20 based on the access authentication information. Is authenticated and the authentication result is notified to the distribution destination terminal 20 (step S42).

At that time, for example, the storage unit (not shown) of the file access management server 30 is searched based on the user identification information included in the access authentication information, and the registered password corresponding to the user identification information is read from the storage unit, and the access authentication is performed. The password included in the information is compared with the registered password read from the storage unit, and it is determined whether or not these passwords match. If these passwords match, the distribution destination terminal 20 is notified that the user of the distribution destination terminal 20 (evaluator) has been authenticated as a regular user.

  When an installation authentication request is received from the distribution destination terminal 20 (NO route in step S41 or YES route from step S42 to step S43), the user (evaluator in charge) of the distribution destination terminal 20 based on the installation authentication information by the installation authentication means 33 Whether the distribution destination terminal 20 is an authorized terminal on which the distribution target software is to be installed, and the authentication result is notified to the distribution destination terminal 20 (see FIG. 6). Step S44).

  At this time, as in the case of the access authentication described above, the storage unit (not shown) of the file access management server 30 is searched by the user identification information included in the installation authentication information, and the registration information (password, Company identification information, server name, global IP address, MAC address, host name, etc.) are read from the storage unit, and the information included in the installation authentication information is compared with the registration information read from the storage unit. It is determined whether the pieces of information match. When these pieces of information match, the distribution destination terminal 20 is notified that the user (evaluator) of the distribution destination terminal 20 is an authorized user and that the distribution destination terminal 20 has been authenticated. The

  Further, when it is time to collect the distribution operation log of the distribution target software at each distribution destination terminal 20, or when the distribution destination software is notified from each distribution destination terminal 20 (NO in step S43) Route or YES route from step S44 to step S45), the log recording unit 34 collects the installation operation log of the distribution target software in each distribution destination terminal 20 (step S46), and the collected or notified installation operation log is stored in the database. Etc. (step S47).

  Then, the installation operation log recorded in the database or the like is referred to (step S48), and if there is a distribution destination terminal 20 that has successfully installed the distribution target software (YES route in step S49), the installation operation restriction means 35 The subsequent distribution target software installation operation is prohibited in the distribution destination terminal 20 (step S50). On the other hand, if there is no distribution destination terminal 20 that has successfully installed the distribution target software (NO route of step S49), the process of step S50 is skipped.

  Further, when there is a re-installation request for the distribution target software from the distribution destination terminal 20 that has successfully installed the distribution target software (NO route in step S45, NO route in step S49, or YES route in step S50 to step S51). The file access management server 30 asks the administrator whether or not to permit reinstallation, receives an instruction from the administrator (step S52), and instructs the administrator to permit the reinstallation. (YES route of step S53), the distribution destination terminal 20 that has made the reinstallation request is temporarily released from the prohibited state of the installation operation by the installation operation restricting means 35 (step S54), and the distribution destination that has made the reinstallation request Software to be distributed at terminal 20 It becomes possible to perform the re-installation of the software. When the administrator gives an instruction not to permit reinstallation (NO route of step S53), the process of step S54 is skipped.

Also, when it is time to collect the results of operation evaluation of software executed at each distribution destination terminal 20, or when notification of the result of operation evaluation is received from each distribution destination terminal 20 (NO route of step S51 or The NO route in step S53 or the YES route from step S54 to step S55), the management means 31 collects the results of the operation evaluation of the distribution target software from the terminal 20 of each person in charge of evaluation (step S56), and is collected or notified. The result of the operation evaluation (“good (OK)” or “NG”) is recorded in a database or the like in association with each distribution destination terminal 20 (step S57).

  Then, the result of the operation evaluation recorded in the database or the like is referred to by the management means 31 (step S58), and the response “good (OK)” is received as an operation evaluation result from all the distribution destination terminals 20 (step S58). (YES route in S59), any one of the above items (11) to (16) is managed (step S60). If there is no reply “good (OK)” from all the distribution destination terminals 20 (NO route of step S59), the process of step S60 is skipped. Note that if the operation evaluation result is not received and the notification of the operation evaluation result is not received from each distribution destination terminal 20 (NO route in step S55), or after the process in step S60, the process returns to step S41.

[3] Effects of the Software Management System of the Present Embodiment As described above, according to the software management system 1 as an embodiment of the present invention, when distributing software to be distributed, access authentication, installation authentication, Are double-authenticated, and the distribution target software is installed only on the legitimate user's legitimate terminal (distribution destination terminal) 20 and is executed only on the legitimate user's legitimate terminal (distribution destination terminal) 20. In addition, since the distribution target software is installed only by the dedicated installer 53 in the distribution file set 50, as described above, evaluation of a pre-commercial product (for example, a printer driver) and its associated software is performed. Therefore, the software is distributed to the evaluator (user) and the evaluator's terminal (distribution destination) When installing on a terminal 20, it is possible to more reliably prevent external leakage and unauthorized use of software including highly confidential information (external secret information) related to pre-market products with a simple method. .

  At the time of installation authentication by the installation authentication means 33, the distribution destination terminal 20 that made the access authentication request is the same as the distribution destination terminal 20 that made the installation authentication request, or the distribution destination terminal 20 that made the installation authentication request specifies And the distribution destination terminal 20 to which the software to be distributed is to be installed is set as an installation authentication condition that the distribution destination terminal 20 that issued the installation authentication request is a predetermined address. Installation authentication conditions are set more severely, and external leakage and unauthorized use of distribution target software can be prevented more reliably. Here, by using the global IP address as the installation authentication condition, the distribution target software can be installed in the distribution destination terminal when the distribution destination terminal 20 exists at a predetermined position specified by the global IP address.

Note that although authentication is performed using a global IP address (location location check of the distribution destination terminal 20), for example, a GPS (Global Positioning System) provided in the distribution destination terminal 20 is used instead of the global IP address. A function may be used. In that case, at the time of installation authentication, the current location (latitude / longitude information) of the distribution destination terminal 20 detected by the GPS function is notified to the file access management server 30 as installation authentication information. Only when the location (latitude / longitude information) included in the information is at a predetermined position (for example, in-house), installation is permitted, that is, it is authenticated that the distribution destination terminal 20 is a regular terminal.

In the file access management server 30, the log recording unit 34 is provided with the distribution destination terminal 20.
By collecting and recording the installation operation log of the distribution target software in, the distribution target software is recorded as to which terminal 20 by whom and when the distribution target software is installed. When an unauthorized installation is detected, it is possible to analyze the unauthorized use or unauthorized installation based on the installation operation log.

  At that time, the file access management server 30 refers to the installation operation log, and the distribution operation of the distribution target software is performed for the distribution destination terminal 20 for which the distribution target software has been successfully installed by the installation operation restriction means 35. (Or access to the distribution target software from the PDF file) is prohibited, so that installation of the distribution target software is prevented many times, and external leakage and unauthorized use of the distribution target software are prevented. , Can be more reliably prevented.

  However, when the file access management server 30 requests the reinstallation of the software to be distributed from the distribution destination terminal 20 after prohibiting the installation operation as described above, the installation operation (or according to the instructions of the administrator) It is necessary to re-install the installed distribution target software for some troubles, etc. by temporarily releasing the prohibition status of the distribution target software from the PDF file) In such a case, re-installation is possible with the approval of the administrator, so that convenience at the distribution destination terminal 20 is not impaired.

  Further, in the software management system 1 as described above, when the distribution target software is related to a product to be released at a predetermined date and time, the setting unit 14 causes the distribution source terminal 10 to perform the process up to the predetermined date and time. By setting it as an accessible period, the software is distributed to the evaluator (user) and the evaluator's terminal is used to evaluate the pre-market product and the accompanying software as described above. In the case of installation in the (distribution destination terminal) 20, the software and the encrypted file 52 can be accessed for evaluation until the predetermined date and time, and when the predetermined date and time is reached, the software and encryption are automatically performed. Access to the activation file 52 becomes impossible, and unauthorized use of software related to a commercially available product is more reliably prevented. Door can be.

  On the other hand, if the distribution target software is distributed to a plurality of distribution destination terminals 20 and is subjected to operation evaluation by each distribution destination terminal 20, the file access management server 1 receives the distribution target software from all distribution destination terminals 20. All the distribution destination terminals are collected by changing the access authority or the accessible period for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 according to the collected evaluation results. 20 can manage access to the encrypted file 52 and the distribution target software.

  For example, as in item (11) above, the distribution target software is related to a product released at a predetermined date and time, and the evaluation result from all distribution destination terminals 20 is “good (OK)”. If the answer is obtained, the access period for the encrypted file 53 and the distribution target software by all the distribution destination terminals 20 is changed by the predetermined date and time, so that the automatic operation is performed when the predetermined date and time are reached. Therefore, access to the software and the encrypted file 52 becomes impossible, and unauthorized use of software related to a commercially available product can be prevented more reliably. On the other hand, as described in the item (12), when it is determined that the software need not be kept confidential at the same time as the release, the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 at the predetermined date and time. By changing the access authority to the software so that all types of access can be made, it is possible to automatically make the access to the software and the encrypted file 52 free at a predetermined date and time.

  In addition, as described in item (13) above, the distribution target software is related to a product that is released after the completion of evaluation by a plurality of distribution destination terminals 20, and the evaluation results are obtained from all distribution destination terminals 20. When an answer of “Good (OK)” is obtained, the product release date is determined, and the access period for the encrypted file 52 and the distribution target software by all the distribution destination terminals 20 is determined. By changing the setting to the release date, access to the software and the encrypted file 52 is automatically disabled when the release date is reached, and unauthorized use of software related to commercially available products is more reliably prevented. be able to. On the other hand, as described in the above item (14), when it is determined that the software need not be kept confidential at the same time as the release, the encrypted file 52 and the distribution by all the distribution destination terminals 20 are determined at the determined release date and time. By changing the access authority for the target software so that all types of access can be made, the access to the software and the encrypted file 52 can be automatically made free when the date of publication is reached. In this case, since the release date and time can be determined at the time when the evaluation of all the evaluators is completed, the release date and time can be set earlier when the operation evaluation is completed earlier.

  Further, as in the above item (15), when all the distribution destination terminals 20 have answered “good (OK)” as the evaluation result, regardless of the product release date, all the distribution destination terminals 20 By changing the access authority or access period for the encrypted file 52 and the distribution target software to all types of inaccessible, the software and the encrypted file 52 cannot be automatically accessed at that time. Thus, unauthorized use of software related to a commercially available product can be prevented more reliably.

[4] Others The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present invention.
For example, in the above-described embodiment, the software management system 1 uses the software as a distribution target software as a distribution target software in order to evaluate a pre-commercial product (for example, a printer driver) and software associated therewith. Although it is applied as a countermeasure against leakage when distributed to multiple evaluation personnel (users) in a company, etc., the present invention is not limited to this and uses various highly confidential software. It can be applied to the case where the software is provided and installed to the user, or the case where various software is charged and provided to the user, and the same effect as described above can be obtained.

Further, the functions (all or a part of functions of each means) as the above-described means 11 to 15, 21 to 26, and 31 to 35 are determined by a computer (including a CPU, an information processing apparatus, and various terminals) as a predetermined application program. It is realized by executing.
The program is, for example, a computer such as a flexible disk, CD (CD-ROM, CD-R, CD-RW, etc.), DVD (DVD-ROM, DVD-RAM, DVD-R, DVD-RW, DVD + R, DVD + RW, etc.). It is provided in a form recorded on a readable recording medium. In this case, the computer reads the predetermined application program from the recording medium, transfers it to the internal storage device or the external storage device, and uses it. Further, the program may be recorded in a storage device (recording medium) such as a magnetic disk, an optical disk, or a magneto-optical disk, and provided from the storage device to a computer via a communication line.

Here, the computer is a concept including hardware and an OS (operating system), and means hardware operating under the control of the OS. Further, when the OS is unnecessary and the hardware is operated by the application program alone, the hardware itself corresponds to the computer. The hardware includes at least a microprocessor such as a CPU and means for reading a program recorded on a recording medium. The predetermined application program includes a program code that causes the computer as described above to realize the functions of the units 11 to 15, 21 to 26, and 31 to 35. Also, some of the functions may be realized by the OS instead of the application program.

  Furthermore, as a recording medium in the present embodiment, in addition to the flexible disk, CD, DVD, magnetic disk, optical disk, and magneto-optical disk described above, an IC card, ROM cartridge, magnetic tape, punch card, computer internal storage device (RAM) In addition, various computer-readable media such as an external storage device or a printed matter on which a code such as a barcode is printed can be used.

It is a block diagram which shows the structure of the software management system as one Embodiment of this invention. It is a schematic diagram for demonstrating the file set production operation for distribution in the software management system (distribution origin terminal) of this embodiment. It is a schematic diagram for demonstrating the installation operation | movement of the software for distribution in the software management system (distribution destination terminal) of this embodiment. It is a flowchart for demonstrating operation | movement (distribution file set creation operation | movement) of the distribution origin terminal in the software management system of this embodiment. It is a flowchart for demonstrating operation | movement (distribution target software installation operation | movement) of the distribution destination terminal in the software management system of this embodiment. It is a flowchart for demonstrating operation | movement of the file access management server in the software management system of this embodiment.

Explanation of symbols

1 Software management system 10 Distribution terminal (client PC; personal computer)
DESCRIPTION OF SYMBOLS 11 Conversion means 12 Attachment means 13 Encryption means 14 Setting means 15 Creation means 20 Distribution destination terminal (client PC; personal computer)
DESCRIPTION OF SYMBOLS 21 Access authentication request means 22 Decoding means 23 Installation authentication request means 24 Extraction means 25 Installation means 26 Permitting means 30 File access management server 31 Management means 32 Access authentication means 33 Installation authentication means 34 Log recording means 35 Installation operation restriction means 40 Network 50 File set for distribution 50A Recording medium 51 Plug-in 52 Encrypted file 53 Dedicated installer

Claims (17)

A distribution source terminal that creates a distribution file storing the distribution target software in order to distribute the distribution target software;
A distribution destination terminal to which the distribution file created by the distribution source terminal is distributed and the distribution target software stored in the distribution file is to be installed;
A file access management server for managing access to the distribution file distributed from the distribution source terminal to the distribution destination terminal;
The distribution source terminal is
Conversion means for converting a document file including information relating to the distribution target software into a completed document file having a container function;
Using the container function of the completed document file converted by the converting means, attachment means for attaching the distribution target software to the completed document file;
Encryption means for encrypting the completed document file attached with the distribution target software by the attachment means with a predetermined encryption key managed by the file access management server, and creating an encrypted file;
File access management by setting user information relating to a user who is permitted to access the encrypted file created by the encryption means and access information permitted for the user and access information relating to an accessible period Setting means for notifying the server;
Creation of creating a distribution file set including the encrypted file created by the encryption means and a dedicated installer for installing the distribution target software included in the encrypted file on the distribution destination terminal as the distribution file With means,
The distribution destination terminal is
Prior to accessing the encrypted file of the distribution file set distributed from the distribution source terminal, access authentication information is notified to the file access management server, and the user of the distribution destination terminal accesses the encrypted file. Access authentication requesting means for requesting access authentication as to whether or not the authorized user is authorized,
In response to an access authentication request from the access authentication requesting means, when the notification that the user of the distribution destination terminal is authenticated is received from the file access management server, the encrypted file is returned to the original Decryption means for decrypting into a completed document file and enabling access according to the access information set for the encrypted file;
By executing the dedicated installer after decrypting the encrypted file by the decryption means, the installation access information is notified to the file access management server, and the user of the distribution destination terminal installs the distribution target software. Installation authentication request means for requesting installation authentication as to whether or not the authorized user is authorized and the distribution destination terminal is the authorized terminal to which the distribution target software is to be installed, and the installation authentication request means When the file access management server receives a notification from the file access management server to authenticate that the user of the distribution destination terminal is an authorized user and that the distribution destination terminal is an authorized terminal. Extracting the software to be distributed from the completed document file, and the extracting means Ri and out the said distributed target software is configured to include a processing means which acts as an installation means for installing the said distribution destination terminal,
The file access management server is
Management means for managing the user's access to the encrypted file and the software to be distributed based on the user information and the access information set and notified by the setting means of the distribution source terminal;
When receiving the access authentication request from the distribution destination terminal, it authenticates whether or not the user of the distribution destination terminal is an authorized user based on the access authentication information, and displays the authentication result as the distribution destination terminal. An access authentication means to notify
When receiving the installation authentication request from the distribution destination terminal, based on the installation authentication information, whether or not the user of the distribution destination terminal is an authorized user, and the distribution destination terminal determines the software to be distributed. A software management system comprising: an installation authentication unit that authenticates whether or not the terminal is a regular terminal to be installed and notifies the distribution destination terminal of the authentication result.   One of the installation authentication conditions is that the installation authentication means of the file access management server has the same distribution destination terminal that made the access authentication request and the distribution destination terminal that made the installation authentication request. The software management system according to claim 1, wherein:   The installation authentication means of the file access management server uses one of the installation authentication conditions that the distribution destination terminal that has made the installation authentication request is a specific terminal. Item 3. The software management system according to item 2. One of the installation authentication conditions is that the installation authentication means of the file access management server uses a global IP (Internet Protocol) address of a distribution destination terminal that has made the installation authentication request as a predetermined address. The software management system according to any one of claims 1 to 3. The distribution destination terminal is
While the access to the distribution target software from the original completed document file decrypted by the decryption means is prohibited, the distribution from the file access management server in response to an installation authentication request by the installation authentication request means When the user of the destination terminal is a regular user and receives notification that the distribution destination terminal is authenticated, the access to the distribution target software from the original completed document file is accessed. The software management system according to any one of claims 1 to 4, further comprising permission / rejection means for permitting.   6. The distribution file set created by the creation means of the distribution source terminal is distributed to the distribution destination terminal via a network. 6. The distribution file set according to claim 1, wherein the distribution file set is distributed to the distribution destination terminal via a network. The software management system described.   6. The distribution file set created by the creation means of the distribution source terminal is distributed to the distribution destination terminal in a state of being recorded on a recording medium. The software management system according to claim 1. The file access management server is
The log recording means for collecting and recording the installation operation log of the distribution target software in the distribution destination terminal is configured to be configured. Software management system. The file access management server is
Refer to the installation operation log collected by the log recording means, and for the distribution destination terminal that has successfully installed the distribution target software, the installation operation restriction prohibits the subsequent installation operation of the distribution target software. 9. The software management system according to claim 8, wherein the software management system comprises means. The file access management server is
If the distribution destination terminal makes a re-installation request for the software to be distributed after the installation operation restriction unit prohibits the installation operation, the installation operation restriction unit prohibits the installation operation according to an instruction from the administrator. The software management system according to claim 9, wherein the software management system is configured to temporarily cancel the state. The distribution target software relates to a product released at a predetermined date and time,
The software management system according to any one of claims 1 to 10, wherein the setting unit of the distribution source terminal sets the period until the predetermined date and time as the accessible period. The distribution target software is distributed to a plurality of distribution destination terminals and is subjected to operation evaluation by each distribution destination terminal.
The management unit of the file access management server collects evaluation results of the distribution target software from all the distribution destination terminals, and is set by the setting unit of the distribution source terminal according to the collected evaluation results 11. The system according to claim 1, wherein the access authority or the accessible period for the encrypted file and the software to be distributed by all the distribution destination terminals is changed. The software management system according to claim 1. The distribution target software relates to a product released at a predetermined date and time,
When the management means of the file access management server gives good evaluation results from all the distribution destination terminals, the period during which all the distribution destination terminals can access the encrypted file and the distribution target software 13. The software management system according to claim 12, wherein the setting is changed by the predetermined date and time. The distribution target software relates to a product released at a predetermined date and time,
When the management means of the file access management server gives good evaluation results from all the distribution destination terminals, the encrypted file and all the distribution targets by all the distribution destination terminals at the predetermined date and time. 13. The software management system according to claim 12, wherein the access authority for the software is changed so that all types of access can be made. The distribution target software relates to a product released after the evaluation by the plurality of distribution destination terminals is completed,
The management means of the file access management server determines the release date of the product when the evaluation results from all the distribution destination terminals are good, and the encrypted file and all the distribution destination terminals 13. The software management system according to claim 12, wherein an access period for the distribution target software is changed to the determined release date and time. The distribution target software relates to a product released after the evaluation by the plurality of distribution destination terminals is completed,
The management means of the file access management server determines the release date and time of the product when the evaluation results from all the distribution destination terminals are good, and all the distributions are performed at the determined release date and time. 13. The software management system according to claim 12, wherein the access authority for the encrypted file and the distribution target software by the destination terminal is set and changed so as to be accessible for all types.   The management means of the file access management server, when the evaluation results from all the distribution destination terminals become good, access authority to the encrypted file and the distribution target software by all the distribution destination terminals or 13. The software management system according to claim 12, wherein the accessible period is changed to all types of inaccessible.

Images