JP7272156B2 - Information processing device, information processing method - Google Patents

Description

The present invention relates to an information processing device and an information processing method.

In general, when developing a program, multiple parties such as developers and evaluators access the source code of the program stored in a server or the like (eg, Patent Document 1).

JP 2014-279012 A

By the way, if the number of people involved in program development increases, for example, there is a risk that someone pretending to be a related person will rewrite the source code, or that part of the program's test items will not be performed due to mistakes, and the program will not be executed. Increased risk of being released. As a result, problems may occur when the program is executed.

SUMMARY OF THE INVENTION The present invention has been made in view of the conventional problems as described above, and an object of the present invention is to provide a technique that can prevent problems from occurring when a developed program is executed.

The main aspect of the present invention for solving the above-mentioned problems is to provide a first adding unit for adding a first electronic signature of a creator who created a source code of a program to the source code; and a storage unit that stores the source code in a storage unit.

ADVANTAGE OF THE INVENTION According to this invention, the technique which can suppress that a problem arises when the developed program is run can be provided.

1 is a diagram showing a configuration of an information processing device 10; FIG. 3 is a diagram for explaining the details of the information processing apparatus 10; FIG. 6 is a diagram showing an example of information stored in an authentication information DB 60; FIG. 6 is a diagram showing an example of configuration management information 62. FIG. 4 is a flowchart showing an example of processing executed by the information processing apparatus 10; 4 is a flowchart showing an example of processing executed by the information processing apparatus 10; 6 is a flowchart showing an example of electronic signature processing; FIG. 10 shows source code Xi with an electronic signature 100i; FIG. 4 shows source code Xi with electronic signatures 100i and 101i; FIG. 10 is a diagram showing a binary code Yi with an electronic signature 200i; FIG. 4 shows source code Xi with electronic signatures 100i-102i; FIG. 10 is a diagram showing a binary code Yi with an electronic signature 201i;

At least the following matters will become apparent from the descriptions of this specification and the accompanying drawings.

=====This Embodiment=====
<<<configuration of information processing apparatus 10>>>
FIG. 1 is a diagram showing a hardware configuration example of an information processing apparatus 10 of this embodiment. The information processing apparatus 10 is a server that supports program configuration management and stores programs to be developed.

Here, "program configuration management" means, for example, updating and managing a developed program together with its version number (hereinafter simply referred to as "version"). Therefore, by referring to information (to be described later) indicating configuration management of the program, it is possible to reproduce the past state of the program as necessary.

Further, in the present embodiment, the "program to be developed" is, for example, for setting the operation of the embedded devices 15a to 15c incorporated in controllers in the FA field, vending machines, etc. Source code, binary including code.

The information processing device 10 includes a CPU (Central Processing Unit) 20 , a memory 21 , a storage device 22 , an input device 23 , a display device 24 and a communication device 25 .

The CPU 20 implements various functions of the information processing apparatus 10 by executing programs stored in the memory 21 and the storage device 22 .

The memory 21 is, for example, a RAM (Random Access Memory) or the like, and is used as a temporary storage area for programs, data, and the like.

The storage device 22 is, for example, a non-volatile storage means area such as a hard disk, and stores programs and various data.

The input device 23 is, for example, a keyboard or a touch panel, and is a device that receives an input of a user's operation result. The display device 24 is, for example, a display, and is a device that displays the processing result.

The communication device 25 is an appropriate communication means such as a network interface, and transmits and receives data to and from the built-in devices 15a to 15c via the network 11. FIG. Although details will be described later, the embedded devices 15a to 15c are devices capable of verifying an electronic signature (described later) of an "administrator" who manages program development.

<<Function Blocks Implemented in Information Processing Apparatus 10, etc.>>
FIG. 2 is a diagram showing functional blocks implemented in the information processing apparatus 10 and information stored therein. In the information processing apparatus 10 , a storage unit 50 , a configuration management unit 51 and a communication unit 52 are implemented by executing a predetermined program (not shown) stored in the storage device 22 by the CPU 20 .

== Information in Storage Unit 50 ==
The storage unit 50 is, for example, a storage area assigned to the storage device 22, and stores an authentication information DB (DB: database) 60, program DBs 61 and 63, configuration management information 62 and 64, and a device information DB 65. FIG.

For example, as shown in FIG. 3, the authentication information DB 60 includes various information related to authentication of the user of the information processing device 10 and the like. Specifically, the authentication information DB 60 includes "User ID" indicating the identification information of the user, "PW" indicating the password of the user, and "user name" of the user.

Furthermore, the authentication information DB 60 includes “authority” indicating user authority and “key information” indicating user public key information. “User authority” refers to whether the user is the “creator (or developer)” of the program, the “evaluator” of the program, the “tester” of the program, or the It is distinguished by whether it is the "manager" of the development.

A "public key" is key information for a "secret key" (described later) that is assigned to each of a plurality of users and used when attaching an electronic signature to various types of information.

For example, the first line in FIG. 3 indicates that "User ID" is "001", "PW" is "abc12", and "user name" is "A1". Therefore, when "A1" accesses the information processing apparatus 10 using "001" as "User ID" and "abc12" as "PW", in the information processing apparatus 10, "A1" It becomes possible to execute processing according to the “creator”, which is the “authority” of .

The program DB 61 is a database containing source codes Xi for each of a plurality of developed programs i. Although the details will be described later, the source code Xi is attached with an “electronic signature” of a person involved in program development.

The configuration management information 62 is information related to configuration management of the source code Xi. For example, as shown in FIG. information that contains

By the way, the source code is generally evaluated every time the source code is updated to implement a predetermined function before the program is released. Then, if there is a problem with the evaluation result, the source code is modified. On the other hand, if there is no problem in the evaluation result, the source code is converted into binary code, installed in the target device of the program (for example, embedded device 15a), and tested.

If there is a problem with the test results, the source code is corrected, but if there are no problems with the test results, the program is released to other devices.

Here, for example, if a person pretending to be the "creator" or "evaluator" of the source code accesses the source code in the program DB 61, the program may include illegal processing as a result.

Also, if the "tester" of the binary code converted from the source code fails to conduct part of the test due to a mistake, the program may be released with bugs.

Although details will be described later, in this embodiment, in order to prevent such a situation, every time work such as updating or evaluating the source code of the developed program is performed, the "electronic signature" of the person who performed the work is added. is attached to the source code and stored in the storage unit 50 .

In general, it is possible to attach an "electronic signature", to ensure that the source code has not been tampered with, and to authenticate the signer of the "electronic signature". As a result, even if there is a problem with the program after the program is released, it is possible to reliably identify the parties involved in the problem program.

As a result, for example, it is possible to prevent mistakes such as spoofing of the "creator" of the source code and mistakes such as part of the test being incorrectly performed, so when the developed program is executed as a result It is possible to suppress the occurrence of problems.

For example, the first line in FIG. 4 indicates that the “version” of the source code X1 is “2.0” and the “electronic signature” of the creator “A2” is attached to the source code X1. indicates

The program DB 63 is a database containing binary code Yi corresponding to source code Xi. Although the details will be described later, the "electronic signature" of the "tester" or "administrator" is attached to the binary code Yi.

The configuration management information 64 is information about the binary code Yi, and is information including, for example, the relationship between the "version" of the binary code Yi and the "electronic signature" attached to the binary code Yi.

The device information DB 65 is a database containing information on embedded devices 15a to 15c, which are destinations of developed programs (here, binary code).

== Functional Blocks of Configuration Management Unit 51 ==
The configuration management unit 51 is a block mainly for performing configuration management of programs to be developed, and includes a first granting unit 70, a second granting unit 71, a third granting unit 72, a fourth granting unit 73, a storage unit 74, It includes an update unit 75 , an acquisition unit 76 , a determination unit 77 and a generation unit 78 .

The first granting unit 70 grants the “electronic signature” of the “creator” of the source code Xi to the source code Xi.

The second granting unit 71 grants the “electronic signature” of the “evaluator” who evaluates the source code Xi to the source code Xi.

The third granting unit 72 grants to the source code Xi the “electronic signature” of the “tester” who tests the binary code Yi obtained by converting the source code Xi.

The fourth granting unit 73 converts either the “electronic signature” of the “tester” or the “electronic signature” (authentication information) of the “administrator” (or “configuration administrator”) who manages the program into a binary Assigned to the code Yi.

The storage unit 74 stores the source code Xi with the “electronic signature” in the program DB 61 of the storage unit 50 . The storage unit 74 also stores the binary code Yi with the “electronic signature” in the program DB 63 of the storage unit 50 .

The update unit 75 updates the configuration management information 62 each time the storage unit 74 stores the source code Xi in the program DB 61 . Furthermore, the updating unit 75 updates the configuration management information 64 each time the storage unit 74 stores the binary code Yi in the program DB 63 .

The acquisition unit 76 acquires the source code Xi to which the “electronic signature” is attached and the binary code Yi to which the “electronic signature” is attached from the storage unit 50 based on the user's operation result or the like.

Based on the evaluation record Ei of the "evaluator", the determination unit 77 determines whether there is a problem in the evaluation result of the source code Xi, and based on the test record Ti of the "tester", determines the binary code Yi It is determined whether or not there is a problem in the test results of .

The generation unit 78 generates a binary code Yi that can be executed by the embedded device 15a or the like from the source code Xi.

== Communication unit 52 ==
The communication unit 52 (transmitting unit) exchanges various information with the embedded devices 15a to 15c, and transmits a release program (here, binary code Yi) to the embedded devices 15a to 15c. As a result, the embedded devices 15a to 15c can execute processing based on the released programs.

<<<Process S10 when creating, evaluating, testing, and distributing a program>>>
5 and 6 are flowcharts showing an example of the processing S10 executed when creating, evaluating, testing, and distributing a program. Note that when using the information processing apparatus 10 of the present embodiment, a user of the information processing apparatus 10 may use a device (for example, a USB token) (not shown) in which information indicating his or her "secret key" is stored. Connect to processing device 10 . As a result, the first attachment unit 70 to the fourth attachment unit 73 of the information processing apparatus 10 can attach the user's "electronic signature" to the data using the user's "secret key". .

==Author Signature==
First, when the "creator" creates the source code Xi of the program, the first attachment unit 70 attaches the "electronic signature" of the "creator" to the source code Xi (S20: first step).

FIG. 7 shows an example of a process 100 executed when adding an "electronic signature", and FIG. 8 is a diagram for explaining the relationship between the source code Xi and the electronic signature 100i of the "creator". be.

First, the first granting unit 70 acquires the source code Xi as data (S200). Next, the first assigning unit 70 calculates a hash value of the acquired source code Xi (S201). Then, the first granting unit 70 encrypts the calculated hash value using the "private key" of the "creator" (S202). When the encryption is executed, the first attachment unit 70 attaches the result of the encryption to the target source code Xi as an electronic signature 100i (S203).

Further, when the process S20 is executed and the electronic signature 100i of the “creator” is attached to the source code Xi, the storage unit 74 stores the source code Xi attached with the electronic signature 100i in the program DB 61 (S21 : second step). The electronic signature 100i corresponds to the "first electronic signature".

Then, when the source code Xi is stored in the program DB 61, the updating section 75 updates the configuration management information 62 (S22). Here, for example, when source code X1 (i=1) created by “creator A2” is stored in the program DB 61, the configuration management information 62 contains “version” of “2.0”, The information on the first line that the “signer” is “creator A2” is added.

When the created source code Xi is stored in the program DB 61, the "evaluator" needs to evaluate whether or not there is a problem with the stored source code Xi based on the development specifications of the program. . Then, when the acquiring unit 76 acquires the source code Xi to which the electronic signature 100i is attached based on the instruction of the “evaluator” (S23: Yes), the determining unit 77 acquires the evaluation record Ei containing information on the evaluation result. , it is determined whether or not there is a problem with the source code Xi (S24).

When the determination unit 77 determines that there is a problem in the evaluation result (S24: Yes), it instructs to correct the source code Xi (S25).

Here, for example, when the source code X2 is newly created by modifying the source code X1, the processes S20 to S22 are executed again. Then, when the source code X2 is created by “creator A2”, the information shown in the second line of FIG. 4 is added to the configuration management information 62 . Therefore, the source code X2 with the “electronic signature” of “creator A2” is stored in the program DB 61 .

== Evaluator signature attached ==
On the other hand, when the determination unit 77 determines that there is no problem with the evaluation result based on the evaluation record Ei (S24: No), the second attachment unit 71 determines that there is no problem, and the electronic signature 100i is attached. An "electronic signature" is attached to the source code Xi (S26). Here, the process of attaching the “electronic signature” to the source code Xi executed in process S26 is basically the same as process S20 (or process S100) described above. However, in the process S26, as shown in FIG. 9, the "data" for calculating the hash value in the process S200 are the evaluation record Ei, the source code Xi, and the electronic signature 100i.

Therefore, here, the electronic signature 101i of the "evaluator" obtained based on these "data" is further attached to the source code Xi attached with the electronic signature 100i. The second attachment unit 71 corresponds to the "second attachment unit", and the electronic signature 101i corresponds to the "second electronic signature".

Then, the storage unit 74 stores the source code Xi to which the electronic signatures 100i and 101i are attached in the program DB 61 (S27). Also, when the source code Xi is stored in the program DB 61, the updating unit 75 updates the configuration management information 62 (S28). For example, the source code when the process S27 is executed is the source code X3 (i=3), the "version" is "2.1", the "creator" is "A2", and the "evaluation When the "person" is "B1", the information on the third line is added to the configuration management information 62. FIG.

== test binary code Yi generation ==
Also, when it is determined that there is no problem in the evaluation result of the source code Xi and the process S27 is executed, the generation unit 78 converts the source code Xi to generate the binary code Yi (S29). This makes it possible to verify the program in an actual device (for example, the built-in device 15a) or the like.

When the binary code Yi is generated, the fourth adding unit 73 adds the electronic signature 200i of the "tester" to the binary code Yi (S30). The binary code Yi with the electronic signature 200i corresponds to the "first binary code".

Here, the process of adding an "electronic signature" to the binary code Yi executed in process S30 is basically the same as the above-described process S20 or the like (or process S100). However, in the process S30, as shown in FIG. 10, the "data" for calculating the hash value in the process S200 is the configuration management information 62 and the binary code Yi. As a result, here, the electronic signature 200i of the "tester" obtained based on these "data" is attached to the binary code Yi.

Then, the storage unit 74 stores the binary code Yi with the electronic signature 200i in the program DB 63 (S31). Also, when the binary code Yi is stored in the program DB 63, the update unit 75 updates the configuration management information 64 (S32).

Here, a test record Ti including the test results is input to the information processing apparatus 10 as a result of the test performed on the actual equipment by the “tester” using the binary code Yi. Then, the determination unit 77 determines whether or not there is a problem in the source code Xi based on the test record Ti (S33).

If the determination unit 77 determines that there is a problem in the test result (S33: Yes), it instructs to correct the source code Xi (S25).

Here, for example, source code X3 shown in FIG. 4 is tested, and if it is determined that there is a problem in the test result, corrected source code X4 is newly created. Then, the processes S20 to S22 and the like described above are executed. As a result, when the new source code X4 is created by “creator A1”, the information shown in the fourth line in FIG. 4 is added to the configuration management information 62. Further, the source code X4 to which the “electronic signature” of “creator A1” is attached is stored in the program DB61. After that, the processing up to processing S33 is executed for the source code X4.

==Examiner's Signature Granted==
On the other hand, if the determination unit 77 determines that there is no problem with the test results (S33: No), the third attachment unit 72 applies Then, the "electronic signature" of the "tester" is given (S34).

Here, the process of attaching the “electronic signature” to the source code Xi executed in process S34 is basically the same as process S20 (or process S100) described above. However, in the process S34, as shown in FIG. 11, the "data" for calculating the hash value in the process S200 are the evaluation record Ei, the test record Ti, the source code Xi, and the electronic signatures 100i and 101i.

Therefore, here, the electronic signature 102i of the "tester" obtained based on these "data" is added to the source code Xi attached with the electronic signatures 100i and 101i. The electronic signature 102i corresponds to the "third electronic signature".

Then, the storage unit 74 stores the source code Xi to which the electronic signatures 100i to 102i are attached in the program DB 61 (S35). Also, when the source code Xi is stored in the program DB 61, the updating unit 75 updates the configuration management information 62 (S36). For example, the source code when the process S36 is executed is the source code X6 (i=6), the "version" is "2.2", the "creator" is "A1", and the "evaluation When the “tester” is “B2” and the “tester” is “C3”, the information on the sixth line is added to the configuration management information 62 .

== Binary Code Yi Generation for Release ==
When the source code Xi to which the electronic signatures 100i to 102i of all related parties are added is stored, and the configuration management information 62 is updated in processing S36, the generation unit 78 converts the source code Xi to generate the binary code Yi. Generate (S37). As a result, a program (binary code Yi) that is released to and executed by an actual device (for example, embedded device 15a) is generated.

When the binary code Yi is generated, the fourth adding unit 73 adds the electronic signature 201i of the "administrator" to the binary code Yi (S38). The electronic signature 201i of the "administrator" corresponds to the "fourth electronic signature", and the binary code Yi attached with the electronic signature 201i of the "administrator" corresponds to the "second binary code".

Here, the process of adding the "electronic signature" to the binary code Yi, which is executed in process S38, is basically the same as the above-described process S20 and the like (or process S100). However, in the process S38, as shown in FIG. 12, the "data" for calculating the hash value in the process S200 are the configuration management information 62 and the binary code Yi. As a result, here, the electronic signature 201i of the "administrator" obtained based on these "data" is attached to the binary code Yi.

Then, the storage unit 74 stores the binary code Yi with the electronic signature 201i in the program DB 63 (S39). Also, when the binary code Yi is stored in the program DB 63, the updating unit 75 updates the configuration management information 64 (S40).

==Distribution of the program==
When the process S40 is performed, the communication unit 52 transmits the binary code Yi with the electronic signature 201i of the "administrator" to each of the embedded devices 15a to 15c.

In the embedded devices 15a to 15c, the binary program Yi is installed only when the electronic signature can be verified using, for example, the "administrator's" electronic signature 201i and the "administrator's" public key. As a result, the embedded devices 15a to 15c can execute programs that are less likely to cause problems.

===Summary===
The information processing apparatus 10 of the present embodiment has been described above. The first attachment unit 70 attaches the electronic signature 100i of the creator to the source code Xi of the created program i. The source code Xi with the electronic signature 100i is stored in the storage unit 50. FIG. As a result, spoofing and the like can be prevented because the creator who created the program can be identified with certainty. Therefore, the possibility of problems occurring when the program is executed can be reduced.

The second adding unit 71 also adds the electronic signature 101i of the “evaluator” to the source code Xi. As a result, for example, the evaluator can be prevented from intentionally omitting a part of the evaluation items, so that the release of problematic programs can be suppressed.

In addition, the generation unit 78 converts the source code Xi to which the electronic signatures of the “creator” and the “evaluator” are attached to the test binary code Yi, and the source code Xi to which the electronic signature is not attached is do not convert. This can improve the quality of testing of the program.

In addition, the third adding unit 72 also adds the electronic signature 102i of the "tester" to the source code Xi. As a result, for example, the tester can be prevented from intentionally omitting a part of the test items, so that the release of problematic programs can be suppressed. Furthermore, in this embodiment, the source code Xi is provided with electronic signatures of all the parties involved. Therefore, if there is a problem with the released program, the person involved in the problem program can be identified with certainty.

In addition, the generation unit 78 converts the source code Xi to which the electronic signatures of the “creator” and the “evaluator” are attached to the binary code Yi for release, and the source code Xi to which the electronic signature is not attached is do not convert. This can prevent programs containing problems from being released.

In addition, since the release binary code Yi is given the electronic signature of the "administrator", the embedded devices 15a to 15c can install only official programs by verifying the electronic signature.

The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit and interpret the present invention. Further, the present invention can be modified and improved without departing from its spirit, and it goes without saying that the present invention includes equivalents thereof.

For example, the generation unit 78 converts the “electronic signature” attached to the source code Xi into the binary code Yi without verifying it, but verifies it using the public key, and only when there is no problem with the verification result, the binary code is It may be converted into code Yi. Even in such a case, as in the present embodiment, it is possible to prevent problems from occurring when the created program is executed.

10 information processing device 20 CPU
21 memory 22 storage device 23 input device 24 display device 25 communication device 50 storage unit 51 configuration management unit 52 communication unit 60 authentication information DB
61, 63 Program DB
62, 64 Configuration management information 65 Device information DB
70 First granting unit 71 Second granting unit 72 Third granting unit 73 Fourth granting unit 75 Update unit 76 Acquisition unit 77 Determination unit 78 Generation unit 100i to 102i, 200i, 201i Electronic signature Xi Source code Ei Evaluation record Ti Test record

Claims (5)

a first granting unit that grants a first electronic signature of a creator who created a source code of a program to the source code;
a storage unit that stores the source code to which the first electronic signature is attached in a storage unit;
When there is no problem in the evaluation result of the source code to which the first electronic signature is attached, the second electronic signature of the evaluator who evaluated the source code to which the first electronic signature is attached is the first electronic signature. a second granting unit that grants to the source code to which is granted;
a generation unit that generates a first binary code based on the source code to which the first and second digital signatures are attached;
If there is no problem in the test of the program executed using the first binary code, the third electronic signature of the tester who tested the program is added to the first and second electronic signatures. and a third granting unit that grants to the source code,
The storage unit is
storing the source code to which the first to third electronic signatures are attached in the storage unit;
An information processing device characterized by: The information processing device according to claim 1 ,
The generating unit
generating a second binary code based on the source code to which the first to third electronic signatures are attached;
An information processing device characterized by: The information processing device according to claim 2 ,
a fourth granting unit that grants, to the second binary code, authentication information that can be verified by a device that transmits the second binary code;
a transmission unit that transmits the second binary code to which the authentication information is attached to the device;
An information processing device comprising: The information processing device according to claim 3 ,
the authentication information is a fourth electronic signature of an administrator who manages the program;
An information processing device characterized by: An information processing method executed by an information processing device,
a first step of attaching a first electronic signature of a creator who created a program source code to the source code;
a second step of storing the source code to which the first electronic signature is attached in a storage unit;
When there is no problem in the evaluation result of the source code to which the first electronic signature is attached, the second electronic signature of the evaluator who evaluated the source code to which the first electronic signature is attached is the first electronic signature. a third step of assigning to the source code assigned with
a fourth step of generating a first binary code based on the source code with the first and second digital signatures;
If there is no problem in the test of the program executed using the first binary code, the third electronic signature of the tester who tested the program is added to the first and second electronic signatures. A fifth step of assigning to the source code;
a sixth step of storing the source code to which the first to third electronic signatures are attached in the storage unit;
An information processing method comprising:

Images