JP2009105566A - Distribution control device and distribution control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file distribution control technique for giving high confidentiality by encryption and facilitating encryption control thereof. <P>SOLUTION: A distribution control server 2 which distributes a file to a terminal 1 having a terminal unique code through a network 3 has a recording unit 21 where the terminal unique code is recorded, a distributed file acquisition unit 23 which acquires a distributed file, an encryption key generation seed setting unit 24c which reads a terminal unique code of each distribution destination terminal out of the recording unit 21 and sets it as an encryption key generation seed, an encryption key generation unit 24d which generates an encryption key for the distributed file using the encryption key generation seed, an encryption unit 24e which encrypts the distributed file using the generated encryption key, and a file distribution unit 24f which distributes the encrypted distributed file to the distribution destination terminal. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a distribution management technique for distributing a file via a network to a terminal having a terminal specific code.

  The file distribution system securely distributes files stored on a server computer via a network to client terminals. The scale of networks such as the Internet and in-house LANs has been expanded, and such a large-scale network makes it possible to exchange information over a wide area, while those who are not legitimate recipients illegally This also increases the risk of obtaining and using files. A typical technique implemented to suppress such illegal file use is file encryption. For example, when performing cryptographic communication between entities, one entity obtains a conversion key using a common key generated using its own private key and shared information that can be shared with the other entity during cryptographic communication. The plaintext is converted into ciphertext with the obtained conversion key and transmitted to the other entity, and the other entity uses the same common key and the shared information as the common key generated using its own private key. A cryptographic communication system that performs cryptographic communication between entities by decrypting a ciphertext transmitted with a conversion key obtained in this way into plaintext has been proposed (see, for example, Patent Document 1). In this cryptographic communication system, it is necessary to determine in advance a secret key and common information unique to the terminal, and the system operation becomes complicated.

JP 2001-156766 A (paragraph numbers 0013, 0041 to 0042, FIG. 2)

  In view of the above situation, an object of the present invention is to provide a file distribution management technique that is highly confidential by encryption and that makes the encryption management simple.

  In order to solve the above problems, a distribution management apparatus according to the present invention is a distribution management apparatus that distributes a file to a terminal having a terminal unique code via a network, and a recording unit that records the terminal unique code; A distribution file acquisition unit that acquires a distribution file, and an encryption key generation type that reads an individual terminal unique code for each distribution destination terminal from the recording unit and sets the terminal unique code as at least one encryption key generation type A setting unit; an encryption key generation unit that generates an encryption key for the distribution file using the set encryption key generation type; and a terminal-specific code held by the distribution destination terminal at least one of the decryption key generation types An encryption unit that encrypts the distribution file using the encryption key, and the encrypted distribution file is pre- It was assumed and a file distribution unit for distributing the distribution destination terminal.

  According to the above configuration, as the key generation type of the encryption key and the decryption key, the terminal unique code that can be specified and extracted on both the distribution management device side and the distribution destination terminal side is used. There is no need to send these key generation seeds for file distribution. In addition, this terminal-specific code is unique to the distribution destination terminal and is substantially unknown to others, and by using this terminal-specific code, the distribution files distributed to each distribution destination terminal are all different encryption keys. Since it is encrypted using, it is highly confidential and it is easy to manage a key that guarantees the confidentiality.

  In one preferred embodiment of the present invention, a security level is set for the distribution file, and an authority level is set for each user of the terminal. It further includes an encryption determination unit that determines whether the distribution file needs to be encrypted based on a result of comparison with the authority level of the user of the file distribution destination terminal.

  According to the above configuration, for example, the distribution file is encrypted when the security level of the distribution file is higher than the authority level of the user of the distribution destination terminal, and is not encrypted when it is low. It is possible to realize a distribution management apparatus capable of performing appropriate encryption as necessary.

  The technical features of the distribution management apparatus according to the present invention described above can also be applied to similar distribution management programs and distribution management methods. For example, the distribution management program according to the present invention distributes a file to a terminal having a terminal unique code via a network, and distributes the file for a distribution management apparatus having a recording unit in which the terminal unique code is recorded. A program, a function for acquiring a distribution file, a function for reading an individual terminal unique code for each distribution destination terminal from the recording unit, and setting the terminal unique code as at least one of encryption key generation types, A function for generating an encryption key for the distribution file using the set encryption key generation seed, and a decryption key generated using at least one of the terminal-specific codes held by the distribution destination terminal as a decryption key generation seed A function for encrypting the distribution file by using the encryption key, and the encrypted distribution file can be decrypted by the distribution tip. To realize a function to distribute to the computer. Naturally, such a distribution management program can also obtain the effects described in the above-described distribution management apparatus, and can further incorporate the above-described additional technology.

[First Embodiment]
Embodiments of a distribution management apparatus according to the present invention will be described below with reference to the drawings.
As shown in FIG. 1, a plurality of terminals 1a, 1b,... (Hereinafter collectively referred to as terminal 1) and a distribution management server 2 as a distribution management apparatus that manages file distribution to the terminal 1 and the like. Connected via the network 3, the file distribution system of the first embodiment is constructed. The network 3 used in this file distribution system may be a relatively small closed network such as an in-house LAN, or a large-scale open WAN including the Internet. A mixed network may be used.

  First, in the computer of the terminal 1a (the same applies to other terminals 1b, etc.), as a function related to the present invention, the terminal unique code table 11 in which the terminal unique code held by itself is registered, the distribution management server 2 A distribution file receiving unit 12 for receiving a distribution file transmitted from the network, a decoding management unit 13 for decoding the received distribution file, a network interface 14 as a transmission / reception unit for transmitting data to the network 3, an output to the monitor 51, and a keyboard A GUI unit 15 that controls input from the operation input device 41 such as a mouse or a mouse is constructed by software and / or hardware.

  When the received distribution file is encrypted, the decryption management unit 13 sets a terminal-specific code registered in the terminal-specific code table 11 as at least one of the decryption key generation types. 13a, including a decryption key generation unit 13b that generates a decryption key using the set decryption key generation seed, a decryption unit 13c that decrypts a distribution file encrypted using the generated decryption key, and the like. Yes.

  The terminal-specific code in the present invention is inherently owned by the terminal, can be specified by the terminal, and can be read only by the terminal itself, and is practically known to others or other terminals. It satisfies the condition of not getting. Examples of satisfying such conditions include a terminal body serial code, a MAC address, a serial code of a program such as an OS installed in the terminal, a CPU number, and a serial code of an embedded device such as a hard disk. Furthermore, the hard disk capacity, the RAM capacity, the CPU clock value, etc. can be used because they can be distinguished by combining them. Further, in some cases, a terminal specific code is generated at a predetermined timing in the terminal, and a dynamic code having a different value every time the terminal specific code is generated can be generated. For example, it can be generated by combining a basic code such as a terminal ID given in advance with a variable code such as a time code that changes over time.

  On the other hand, the computer of the distribution management server 2 includes, as a function related to the present invention, a terminal unique code recording unit 21 that records in advance a terminal unique code of each terminal 1 constructing the file distribution system, and various files. As a file storage unit 22 storing a distribution file, a distribution file acquisition unit 23 for acquiring a distribution file to be distributed to each terminal, a distribution management unit 24 for encrypting the distribution file, and a transmission / reception unit for transmitting data to the network 3 The network interface 25 or the like is constructed by software and / or hardware.

  Here, a schematic diagram of a data structure in the terminal specific code recording unit 21 is illustrated in FIG. As shown in the figure, the terminal unique code recording unit 21 can record a plurality of types of terminal unique codes for each terminal code for identifying a terminal. Note that since this terminal unique code is information that can be known (readable) only by individual terminals, it is collected regularly or irregularly and recorded in advance in the terminal unique code recording unit 21. Such collection is distributed. It may be performed directly through an operation input device (not shown) of the management server 2 or may be collected from the terminal 1 via the network 3. FIG. 3 illustrates the processing flow in the latter case, that is, when the terminal-specific code is collected from the terminal 1 via the network 3. First, the terminal management server 2 requests each terminal 1 to send a terminal unique code (# 01). On the terminal 1 side, a terminal-specific code is read from a specific device or software through a system call attached to the OS or an added-in program, and sent to the terminal management server 2 (# 02). The transmitted terminal unique code is recorded in the terminal unique code recording unit 21 of the terminal management server 2 (# 03). Such terminal-specific codes are collected regularly or irregularly by a terminal-specific code collection unit (not shown). Especially when the above-described dynamic code is adopted as the terminal-specific code, it is matched with the collection timing. It is preferable that the dynamic code is newly generated on the terminal side.

  The file storage unit 22 stores various files acquired via the network 3 or the media drive of the distribution management server 2 (not shown). The file acquisition unit 23 acquires a distribution file from the file storage unit 22 or via the network 3 based on distribution instruction information described later.

  The distribution management unit 24 includes a distribution instruction receiving unit 24a that receives distribution instruction information about a distribution file and its distribution destination terminal, and a distribution file / distribution destination terminal specifying unit that specifies a distribution file and a distribution destination terminal based on the received distribution instruction information. 24b, an encryption key generation type setting unit 24c that reads an individual terminal unique code for each distribution destination terminal from the terminal unique code recording unit 21 and sets the terminal unique code as at least one encryption key generation type. An encryption key generation unit 24d that generates an encryption key for a distribution file using an encryption key generation type, and a terminal unique code held by a distribution destination terminal can be decrypted with a decryption key generated as at least one of the decryption key generation types As described above, the encryption unit 24e encrypts the distribution file using the generated encryption key, and distributes the encrypted distribution file to the distribution destination terminal. It has a such as file distribution unit 24f that.

  Next, based on FIG. 4 and FIG. 5, the flow of the file distribution processing of the file distribution system in the first embodiment will be described. Here, it is assumed that a specific type such as an OS serial code installed in each terminal 1 is set in advance as the terminal unique code to be used.

  First, the flow of processing for encrypting and distributing a distribution file in the distribution management server 2 will be described with reference to FIG. Distribution instruction information for instructing distribution of a specific file to all or a part of the terminals 1 constituting this file distribution system is accepted (# 10). This distribution instruction may be given from any terminal 1 via the network 3, such as instructing the distribution of a specific file from the terminal 1a to the other terminals 1b,. You may perform directly through the operation input device which the server 2 does not illustrate. Further, the distribution instruction information includes at least one of a terminal code and a user name of a distribution destination terminal that distributes the file, in addition to information such as the name of the file to be distributed. When only the user name is used, the terminal used by the user is specified as the distribution destination terminal by the distribution file / distribution destination terminal specifying unit 24b using the authentication information at the time of login of each terminal. Of course, in the case of a system that collects operation logs from each terminal or a system that collects asset information such as software information installed on each terminal, the user name included in such operation logs and asset information It may be specified.

  Based on the received distribution instruction information, the distribution file and the distribution destination terminal are specified (# 20), and the distribution file is acquired from the file storage unit 22 or via the network 3 (# 30). Subsequently, the distribution destination terminals to be processed are sequentially specified from the identified distribution destination terminals (# 40). By using the terminal code of the designated distribution destination terminal, the terminal unique code of the distribution destination terminal is read from the terminal unique code recording unit 21 shown in FIG. 2 (# 50), and this terminal unique code is generated as an encryption key. Set as seed (# 60). Then, an encryption key is generated based on the set encryption key generation type (# 70), and the terminal unique code held by the distribution destination terminal is decrypted with the decryption key generated as the decryption key generation type. The distribution file is encrypted using the encryption key (# 80).

  Then, the encrypted distribution file is distributed to the designated distribution destination terminal 1 (# 90). It is checked whether or not the file distribution to all the specified distribution destination terminals is completed (# 100), and the processes of # 40 to # 90 are repeated until the file distribution to all the distribution destination terminals 1 is completed. . As a procedure for distributing files via the network 3, it is common to adopt a procedure defined in FTP. However, the present invention is not limited to this, and a file using the HTTP protocol is used. Transfer or other file transfer may be used.

  Next, based on FIG. 5, the flow of the decryption process in the terminal that has received the distribution file will be described. Upon receiving the distribution file (# 200), the terminal 1 that has received the encrypted distribution file from the distribution management server 2 reads the corresponding terminal specific code from the terminal specific code table 11 (# 201). The unique code is set as a decryption key generation seed (# 202). Then, a decryption key is generated based on the set decryption key generation type (# 203), and the distribution file is decrypted using this decryption key (# 204). The terminal-specific code that is the generation type of the decryption key matches the terminal-specific code that is the generation type of the encryption key obtained by encrypting the received distribution file (here, installed in the distribution destination terminal 1). Therefore, the encryption key and the decryption key are the same and function as a so-called common key. Therefore, the received distribution file can be decrypted using the generated decryption key.

  According to the above-described embodiment, as the key generation type of the encryption key and the decryption key, the terminal unique code that can be specified and extracted on both the distribution management server 2 side and the distribution destination terminal 1 side is used. There is no need to send keys, decryption keys, or key generation seeds for file distribution. In addition, this terminal-specific code is unique to the distribution destination terminal and is substantially unknown to others, and by using this terminal-specific code, the distribution files distributed to each distribution destination terminal are all different encryption keys. Since it is encrypted using, it is highly confidential and it is easy to manage a key that guarantees the confidentiality.

[Second Embodiment]
Next, a second embodiment of the file distribution system provided with the distribution management device according to the present invention will be described. In the second embodiment, in the first embodiment described above, a security level is set in the distribution file, and an authority level is set for each user of the terminal. A function is provided for determining whether or not the distribution file needs to be encrypted based on the result of comparison with the authority level of the user of the distribution destination terminal of the distribution file.

  FIG. 6 shows a functional block diagram of the file distribution system in the second embodiment. In addition, about the functional element similar to FIG. 1, it represents using the same code | symbol. Although the basic configuration is the same as in FIG. 1, the distribution management server 2 has an authority level recording unit 26 in which the authority level of the terminal user is recorded, and a confidentiality recording unit 27 in which the sensitivity of each file is recorded. And the distribution management unit 24 determines whether the distribution file needs to be encrypted based on a comparison result between the security level of the distribution file and the authority level of the user of the distribution destination terminal of the distribution file. An encryption determination unit 24g is further provided.

  Here, both the authority level of the user and the confidential level of the file are represented by numerical values (points) of 5 levels from 1 to 5, and the authority level is pointed to the authority level recording unit 26 for each user name. The confidentiality level is recorded as a point in the confidentiality recording unit 27 for each file name, but other forms are also possible. Note that these authority level and secret level may be directly input by an operation input device (not shown) of the distribution management server 2 or may be acquired via the network 3.

  Next, the flow of processing in the distribution management server 2 of the file distribution system in the second embodiment will be described with reference to FIG. Detailed description of the same steps as those in FIG. 4 will be omitted. Also, the distribution instruction information in this embodiment includes a user name as a distribution destination. First, distribution instruction information is received (# 10), and a distribution file and a distribution destination terminal are specified (# 20). When the distribution file is acquired (# 30), the encryption determination unit 24g refers to the security level recording unit 27 and checks the file name of the distribution file to acquire the security level (# 31).

  Subsequently, the distribution destination terminals to be processed are sequentially specified from the specified distribution destination terminals (# 40), and the encryption determination unit 24g refers to the authority level recording unit 26, and the user name of the specified distribution destination terminal To obtain the authority level (# 41). Then, the obtained confidentiality level is compared with the authority level to determine whether encryption is necessary (# 42). Here, it is determined that encryption is performed only when the security level of the distribution file is higher than the authority level of the user of the designated distribution destination terminal. Accordingly, when the point of the security level of the distribution file exceeds the point of the authority level (# 42 Yes branch), the same encryption process as in the first embodiment is performed, and the distribution destination terminal to which the encrypted distribution file is designated (# 50 to # 90). On the other hand, if the security level point of the distribution file is equal to or lower than the authority level point (# 42 No branch), skip the steps # 50 to # 80 and proceed to # 90 to specify without encryption. The distribution file is distributed to the specified distribution destination terminal.

  Note that, as in the first embodiment, the above process is performed for all the specified distribution destination terminals (# 100). In the terminal that receives the distribution file, the decryption management unit 13 determines whether or not the distribution file is encrypted. If the distribution file is encrypted, it is decrypted in the same manner as in the process of FIG. Is done.

  By providing an encryption determination function as in the above-described embodiment, appropriate encryption can be performed as necessary. It should be noted that, instead of or in addition to the comparison between the confidential level and the authority level described above, it is of course possible to perform a determination to perform encryption when one of the levels exceeds a predetermined level.

[Third Embodiment]
Next, a third embodiment of the file distribution system provided with the distribution management device according to the present invention will be described. In the first embodiment described above, the encryption key and the decryption key for the distribution file are generated using the terminal-specific code as a generation seed. In the third embodiment, the terminal-specific code is generated as the generation seed for the encryption key and the decryption key. In addition to the code, it also uses file related information related to the distribution file.

  FIG. 8 shows a functional block diagram of the file distribution system in the third embodiment. In addition, about the functional element similar to FIG. 1, it represents using the same code | symbol. Although the basic configuration is the same as in FIG. 1, in this third embodiment, first, file distribution information generation for generating file related information related to the file from the distribution file is performed in the distribution management unit 24 of the distribution management server 2. A distribution information generation unit 24k that generates distribution information describing file-related information. The file-related information can be selected from information related to the distribution file such as the distribution file name, distribution file hash value, distribution file creation date / time, distribution instruction date / time, and distribution execution date / time.

  In the third embodiment, the encryption key generation type setting unit 24c combines the terminal specific code and the file related information as an encryption key generation type for generating an encryption key used for encrypting the distribution file. Set. Further, the file distribution unit 24f distributes distribution information including file related information to each distribution destination terminal together with the distribution file.

  On the other hand, also on the terminal 1 side, the decryption key generation type setting unit 13a generates a decryption key by combining the file related information read from the distribution information distributed together with the distribution file with the terminal specific code read from the terminal specific code table 11. Set as seed.

  Next, based on FIG. 9, the flow of processing in the distribution management server 2 of the file distribution system in the third embodiment will be described. Here, it is assumed that specific types such as the serial code of the OS installed in each terminal 1 and the name of the distribution file are set in advance as the terminal unique code and file related information to be used. Detailed descriptions of the same steps as those in FIG. 4 are omitted.

  First, the distribution instruction information is received (# 10), the distribution file and the distribution destination terminal are specified (# 20), and when the distribution file is acquired (# 30), the name of the acquired distribution file is read and encoded. Is generated as file-related information (# 33).

  Subsequently, the distribution destination terminals to be processed are sequentially designated from the identified distribution destination terminals (# 40), and the terminal unique code of the designated distribution destination terminal is read from the terminal unique code recording unit 21 (# 50). An encryption key generation type is set by combining the terminal specific code and the file specifying code generated in step # 33 (# 60), and an encryption key is generated based on the set encryption key generation type (# 70). ). Then, the distribution file is encrypted using the generated encryption key so that the terminal unique code and the file related information held by the distribution destination terminal can be decrypted with the decryption key generated as the decryption key generation seed (# 80).

  Further, distribution information describing information related to distribution of the encrypted distribution file, here, file-related information used as an encryption key generation type is generated (# 83). Then, the encrypted distribution file and distribution information are distributed to the designated distribution destination terminal 1 (# 90). It is checked whether or not the file distribution to all the specified distribution destination terminals is completed (# 100), and the processes of steps # 40 to # 90 are repeated until the file distribution to all the distribution destination terminals 1 is completed. It is.

  Next, based on FIG. 10, the flow of the decryption process in the terminal that has received the distribution file and the distribution information will be described. First, when an encrypted distribution file and distribution information are received from the distribution management server 2 (# 300), file-related information is read from the distribution information (# 301), and the corresponding terminal-specific code table 11 is associated with the corresponding terminal-specific information. The code is read (# 302). A decryption key generation type is set in combination with the read file related information and the terminal unique code (# 303). Then, a decryption key is generated based on the set decryption key generation type (# 304), and the distribution file is decrypted using this decryption key (# 305). The terminal-specific code and the file-related information that are the generation type of the decryption key match the terminal-specific code and the file-related information that are the generation type of the encryption key obtained by encrypting the received distribution file. Therefore, the encryption key and the decryption key are the same and function as a so-called common key. Therefore, the received distribution file can be decrypted using the generated decryption key.

  If the distribution information distributed from the distribution management server 2 to the terminal 1 is also to be encrypted, it is convenient to encrypt it with an encryption key generated based on the terminal unique code. On the terminal 1 side, the received distribution information is decrypted with a decryption key generated based on its own terminal-specific code to read the file-related information, and then based on this file-related information and its own terminal-specific code The distribution file is decrypted with the generated decryption key.

  By creating the encryption key and the decryption key based on the combination of the terminal unique code and the file related information as in the above-described embodiment, the same terminal is always encrypted with a different encryption key. Security benefits. Note that this embodiment can also have the encryption determination function as in the second embodiment described above.

[Other Embodiments]
(1) In the above-described embodiment, the terminal 1 is provided with the terminal-specific code table 11 and the decoding management unit 13 to realize the decoding function. However, other than this, the distribution file is transferred from the distribution destination terminal 1 to the terminal-specific. You may comprise as an automatic decompression | decompression form which takes in a code and self-decompresses (self-decoding).

(2) In the above-described embodiment, a specific type is set in advance as a terminal-specific code to be used. However, when the terminal 1 has a plurality of types of terminal-specific codes, Correspondingly, it is also preferable to record a plurality of types of terminal unique codes for each terminal in the terminal unique code recording unit 21 and change the type of terminal unique code used for each distribution destination terminal 1. Further, a plurality of types of terminal-specific codes may be used as one encryption key generation type per terminal. At this time, if the type of the terminal-specific code to be used is selected at random, the secrecy is further improved and a security advantage is obtained. Moreover, it is good also as a form which manages time schedules, such as changing the classification of the terminal specific code to be used for every month. In addition, when one selected from a plurality of types of terminal-specific codes is used as an encryption key generation type, a selection information generation unit that generates selection information indicating the type of the selected terminal-specific code is provided. The selection information may be sent to the distribution destination terminal together with the distribution file or separately from the distribution file. In particular, in the form in which distribution information is distributed as in the third embodiment described above, selection information may be included in this distribution information. Note that the file-related information can also employ various forms for the type change as described above.

(3) In the above-described embodiment, the terminal 1 includes an operation log generation unit that describes the operation content of the terminal, and the distribution management server 2 includes an operation log acquisition unit. A specific operation log (for example, the x-th operation log) included in the operation log sequence being started is recorded in both the terminal 1 and the distribution management server 2, and the startup time of such a computer or a specific operation log is recorded. May be regarded as a terminal-specific code and set as a key generation type to generate an encryption key or a decryption key.

(4) In the above-described embodiment, the file storage function, the encryption function, and the file distribution function are integrated into the distribution management server 2 as the distribution management apparatus. A server, an encryption server, and a file distribution server may be used.

(5) In the above-described embodiment, the terminal unique code is not recorded in advance in the terminal unique code table 11 in each terminal 1, but the table is omitted and the decryption key generation type setting unit stores the terminal unique code in hardware. It may be configured to read directly from each part such as software or software.

Functional block diagram of the file distribution system in the first embodiment Explanatory drawing of terminal specific code recording part Flow chart showing collection and recording process of terminal specific code The flowchart which shows the file encryption process in 1st Embodiment The flowchart which shows the file decoding process in 1st Embodiment Functional block diagram of the file distribution system in the second embodiment Flowchart showing file encryption processing in the second embodiment Functional block diagram of the file distribution system in the third embodiment Flowchart showing file encryption processing in the third embodiment The flowchart which shows the file decoding process in 3rd Embodiment

Explanation of symbols

1 Terminal 2 Distribution management server (distribution management device)
11 Terminal Specific Code Table 12 Distribution File Receiving Unit 13 Decryption Management Unit 13a Decryption Key Generation Type Setting Unit 13b Decryption Key Generation Unit 13c Decryption Unit 21 Terminal Specific Code Recording Unit 22 File Storage Unit 23 Distribution File Acquisition Unit 24 Distribution Management Unit 24a Distribution instruction receiving unit 24b Distribution file / distribution destination terminal specifying unit 24c Encryption key generation type setting unit 24d Encryption key generation unit 24e Encryption unit 24f File distribution unit 24g Encryption determination unit 24h File related information generation unit 24k Distribution information generation unit 26 Authority level recording unit 27 Sensitivity recording unit

Claims (3)

A distribution management device that distributes a file over a network to a terminal having a terminal-specific code,
A recording unit for recording the terminal-specific code;
A distribution file acquisition unit for acquiring distribution files;
An encryption key generation type setting unit that reads an individual terminal unique code for each distribution destination terminal from the recording unit and sets the terminal unique code as at least one encryption key generation type;
An encryption key generation unit that generates an encryption key for the distribution file using the set encryption key generation type;
An encryption unit that encrypts the distribution file using the encryption key so that the terminal unique code held by the distribution destination terminal can be decrypted with a decryption key generated as at least one of the decryption key generation types;
A file distribution unit for distributing the encrypted distribution file to the distribution destination terminal;
Distribution management device with A security level is set for the distribution file, and an authority level is set for each user of the terminal.
An encryption determination unit that determines whether or not the distribution file needs to be encrypted based on a comparison result between a security level of the distribution file and an authority level of a user of a distribution destination terminal of the distribution file. 1. The distribution management device according to 1. A distribution management program for a distribution management device that distributes a file to a terminal having a terminal unique code via a network and includes a recording unit in which the terminal unique code is recorded,
The ability to get distribution files,
A function of reading an individual terminal unique code for each distribution destination terminal from the recording unit and setting the terminal unique code as at least one of the encryption key generation types;
A function of generating an encryption key for the distribution file using the set encryption key generation type;
A function of encrypting the distribution file using the encryption key so that the terminal unique code held by the distribution destination terminal can be decrypted with a decryption key generated as at least one of the decryption key generation types;
A function of distributing the encrypted distribution file to the distribution destination terminal;
A distribution management program that enables computers to realize

Images