JP2002244856A - Client-server system for remote operation and method of protecting server in this system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a server having supplied NLO to exclude process requests from programs other than the NLO on a client device to which the NLO has been supplied. SOLUTION: When the client device 2 requests the server 1 to load the NLO, the server 1 acquires a client identifier (IP address) of the client device 2. Then the server 1 transmits the NLO to the client device 2 together with NLO attachment data generated differently every time the NLO is loaded. The NLO loaded to the client device 2 acquires the maintained client identifier of the client device 2 and is shown to the server 1 together with the NLO attachment data. The server 1 issues an NLO identifier and transmits it to the NLO after confirming that the shown client identifier and NLO attachment data are right. The NLO shows the issued NLO identifier at the process requests to the server.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention provides a client device which operates using an NLO (network loadable object) which is a program loaded and operated via a network only when necessary, and an NLO for the client device. The present invention relates to a remote operation client / server system including a server that performs a predetermined process in accordance with a processing request from a provided NLO, and in particular, requests a server that has provided an NLO to process a program other than the NLO provided by the server. The present invention relates to a method for protecting a server in a client / server system for remote operation for protecting the server.

[0002]

2. Description of the Related Art NL which is a program loaded from a server to a client device and executed by the client device
A remote operation client / server system for performing a remote operation (remote operation) using O has been proposed.

In such a client / server system for remote operation, a client device loads an NLO from a server, and the loaded NLO makes a processing request to the server. As a result, the server responds to the processing request from the NLO by the server. Operate managed devices.

In the conventional client / server system for remote operation, the NLO is loaded on the client device and executed. Therefore, the loaded NLO steals or falsifies confidential data of the client device, or operates the client device. The client device is provided with various security mechanisms for protecting the client device from NLO so that unauthorized operations such as stopping the client device cannot be performed.

[0005] However, in the conventional client / server system for remote operation, only the same protection method as that of general server protection is applied to the protection of the server that is accessed from the NLO. That is, a client device that is permitted to connect to the server is registered in the server in advance, and only access from the registered client device is permitted, or a password is required from the user when the NLO is loaded. Only protection methods were used to verify access rights to the site.

Even with such a conventional server protection method, when the NLO processing does not involve a processing request to the server side, there is no problem and it is sufficient. However, in the case where the server performs processing in response to a request from the NLO, such as a client / server system for remote operation, using a conventional method of protecting the server, the server receives a request from a client device that has not loaded the NLO. However, it is not possible to prevent unauthorized access from program modules other than the NLO on the client device loaded with the NLO.

[0007] When an unauthorized access to the server is made from a program module other than the NLO, data transfer that is not permitted by the original NLO is performed between the server and the client device. For example, if the server unconditionally accepts a request from a client device that has loaded an NLO, the operation of the server may be abnormal because data that should not be sent from the original NLO is sent. Or
There is a possibility that the user who has loaded the NLO may gain unauthorized access to data on a server to which access is not permitted.

For this reason, the conventional method of permitting access only from a registered client device, requesting a password from the user when loading the NLO, and confirming the access right to the NLO in the server is used to protect the server. This is not enough.

[0009]

In the above-described conventional remote operation client / server system, the server that has provided the NLO can only confirm whether or not the accessing client device is unauthorized. There has been a problem in that unauthorized access from a program module other than the NLO on the provided client device cannot be excluded.

[0010] It is an object of the present invention to provide a method in which a server that has provided an NLO has an NLO on a client device to which the NLO has been provided.
Another object of the present invention is to provide a client / server system for remote operation that can eliminate a processing request from a program other than the above, and a server protection method in this system.

[0011]

In order to achieve the above-mentioned object, a remote operation client according to the present invention is provided.
A method of protecting a server in a server system includes a client device that operates using an NLO that is a program that is loaded and operated via a network only when necessary, an NLO provided to the client device, and processing from the provided NLO. A method of protecting a server in a client / server system for remote operation including a server that performs a predetermined process according to a request, wherein the client device transmits an NLO request for requesting an NLO load to the server. And when the server receives the NLO request from the client device and permits the client device to load the NLO, obtains a client identifier for identifying the client device that transmitted the NLO request, and executes the loading. The requested NLO, Transmitting to the client device together with NLO attached data, which is data generated differently each time the LO is loaded, wherein the NLO loaded in the client device obtains a client identifier of the held client device And
Presenting the client identifier together with the NLO attached data to the server and transmitting an NLO identifier issuance request to the server; and the server receiving the NLO identifier issuance request from the NLO held in the client device is presented. After confirming that the client identifier and the NLO attached data match the client identifier obtained when the NLO request is received and the NLO attached data attached to the provided NLO, the NLO identifier which is a different value for each provided NLO And the issued N
Transmitting the LO identifier to the NLO that has transmitted the NLO identifier issuance request, the NLO held in the client device presenting the NLO identifier to make a processing request to the server, and a processing request from the NLO. Is received by the server that has received the processing request.
Executing the requested processing after confirming that the LO identifier matches the issued NLO identifier.

According to the present invention, when a server that has provided an NLO to a client device receives a processing request from the client device, the server checks the presence or absence of the NLO identifier to determine whether the processing request is from the provided NLO. It is possible to determine whether the request is from a program module other than the NLO, and it is possible to eliminate a processing request from a program other than the NLO on the client device to which the NLO is provided.

[0013]

Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of a client / server system for remote operation according to an embodiment of the present invention.

The remote operation client / server system according to the present embodiment comprises a server 1 and a client device 2.

The server 1 includes an NLO request processing unit 3 for performing a process requested by the NLO held in the client device 2, an NLO storage unit 4 for storing an NLO 5,
And an identifier management unit 6 for holding and managing the client identifier and the NLO identifier. The client device 2 includes a client identifier holding unit 7 that holds a client identifier for specifying the client device, and an N that executes the NLO loaded from the server 1.
And an LO execution unit 8.

FIG. 2 is a diagram showing the configuration of the identifier management table held in the identifier management unit 6 of the server 1. The identifier management table includes a field for storing a client identifier for identifying a client device,
From the field for storing the NLO attached data attached to the NLO when transmitting the LO to the client device 2 and the field for storing the NLO identifier serving as a permit for permitting a processing request from the NLO held in the client device 2 It is configured.

Next, the operation of the client / server system for remote operation of the present embodiment will be described with reference to FIG.
This will be described in detail with reference to FIG. FIG. 3 is a flowchart showing a procedure from when the client device 2 issues an NLO load request to the server 1 to when the NLO held in the client device 2 issues a processing request to the server 1.

(1) First, the client device 2 presents a user name and a password to the server 1 and issues an NLO load request.

(2) The server 1 determines whether to permit an NLO request from the client device 2. This determination is made by confirming the user name and password.

(3) When permitting the NLO request from the client device 2, the server 1 adds a new column to the identifier management table of the identifier management unit 6, acquires the client identifier of the permitted client device 2, and acquires the client identifier. The written client identifier is written in the added column of the identifier management table.

The client identifier is a number for specifying the client device, and for example, the IP (Internet Protocol) address of the client device 2 can be used. The IP address is an IP address included in a packet (IP packet) of a protocol lower than the application layer protocol used for loading the NLO.
The address can be obtained by reading it from a server-side program. Alternatively, a MAC (Media Access Control) address of a lower-order Ethernet (registered trademark) (Ethernet (registered trademark)) can be used as a client identifier. Also,
Regardless of what protocol is lower than the NLO load protocol, some client device 2 is required to communicate.
Since it is necessary to have unique information, the information can be used as a client identifier.

(4) Next, the server 1 generates NLO attached data and registers it in the column newly created in (2).
Client device 2 attaching LO attached data to NLO
Send to

The NLO attached data created here is:
The data is generated differently each time the NLO is loaded, and is dynamically generated each time the NLO is loaded. The data format of the NLO attached data is not limited as long as it is unique for each load.

For example, NLO program code and NL
A combination of the data of the transmission time of O can be used as the NLO attached data. In this case, the NLO
For example, MIME (Multipurpose Intermediate Intermediate System)
Base6, which is an encoding method of net Mail Extensions
4 and transmitted to the client device 2 together with the NLO.

(5) The NLO loaded into the NLO execution unit 8 of the client device 2 is
It reads and holds the held client identifier of the client device 2 and the NLO attached data attached to itself.

(6) Then, the NLO held in the client device 1 transmits the client identifier and the NLO attached data held in (5) to the server 1, and requests the NLO identifier to be issued.

(7) The server 1 checks the client identifier transmitted from the client device 2 and the NOL attached data with the information described in the identifier management table, and the presented client identifier and the NLO attached data are compared with each other. When the client identifier obtained when the NLO request is received matches the NLO attached data attached to the provided NLO, an NLO identifier is generated, written in a corresponding column of the identifier management table, and the generated NLO identifier is written to the client. It is transmitted to the device 2 side. As the NLO identifier, any value may be used as long as it is different for each provided NLO. For example, a numerical value randomly generated from a client identifier and NLO attached data can be used.

(8) The NLO in the client device 1 that has received the NLO identifier from the server 1 holds the received NLO identifier.

(9) When making a processing request to the server 1, the NLO transmits the NLO identifier held in (8).

(10) The server 1 is a client device 2
When the processing request is received from the NLO in the above, the processing is executed after confirming that the NLO identifier presented from the client device 2 is on the column of the corresponding client device in the identifier management table.

By performing the processing described above, according to the remote operation client / server system of the present embodiment, the server 1 that has provided the NLO 5
When a processing request from the client device 2 is received, N
By confirming the presence or absence of the LO identifier, it is possible to determine whether the processing request is from the provided NLO or a program module other than the NLO,
Processing requests from programs other than the NLO on the client device 2 to which the NLO has been provided can be eliminated.

In this embodiment, the NLO is connected to the server 1
The NLO-attached data transmitted to the client device 2 together with the NLO when the data is loaded into the client device 2 is transmitted in a data format in which anyone can view the contents. However, if a malicious third party plagiarizes the NLO attached data and requests the NLO identifier together with the client identifier, the server 1 determines whether the NLO identifier request is a valid NLO identifier request from the provided NLO. Cannot be determined. Therefore, there is a possibility that an adverse effect of issuing an NLO identifier to a malicious third party may occur.

To prevent such adverse effects, for example,
First, the NLO attached data is encrypted and transmitted to the client device 2 together with the NLO. When the NLO is started on the client device 2 side, the encrypted attached data is decrypted and sent back to the server 1 by an internal routine of the NLO. It may be. By doing so, as long as the internal routine of the NLO is not decrypted, the server 1
The request for the O identifier is the NLO provided by server 1.
You can confirm that you are yourself. Then, as a sign of the NLO authentication, N
If the LO identifier is used, a long data length N
Processing can be performed without sending back LO attached data.

[0035]

As described above, according to the present invention,
The server that has provided the NLO can obtain an effect that a processing request from a program other than the NLO on the client device to which the NLO has been provided can be excluded.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a client / server system for remote operation according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a configuration of an identifier management table stored in an identifier management unit 6 in FIG.

FIG. 3 is a flowchart showing the operation of the remote operation client / server system of FIG. 1;

[Explanation of symbols]

 Reference Signs List 1 server 2 client device 3 NLO request processing unit 4 NLO storage unit 5 NLO 6 identifier management unit 7 client identifier holding unit 8 NLO execution unit

Claims (8)

[Claims] 1. A client device that operates using an NLO, which is a program that is loaded and operated via a network only when necessary, and an NL that is connected to the client device.
A client server system for remote operation, comprising: a server that provides an O.O. and performs predetermined processing in accordance with the processing request from the provided NLO. When permitting the load, the client identifier for identifying the client device that has transmitted the NLO request is acquired, and the NLO requested to be loaded is acquired.
Is transmitted to the client device together with the NLO attached data which is data generated differently each time the NLO is loaded, and the NL loaded in the client device is transmitted.
When a request for issuing the client identifier and the NLO identifier presenting the NLO attached data from O is received, the presented client identifier and the NLO attached data are attached to the client identifier acquired when the NLO request was received and the provided NLO. After confirming that the received NLO data matches the NLO attached data, the NLO identifier that is different for each provided NLO is issued, and the issued NLO identifier is transmitted to the client device that transmitted the NLO identifier issuance request. Receiving the processing request from the NLO, the NLO identifier presented with the processing request
A server that executes the requested processing after confirming that it matches the identifier, sends an NLO request for requesting an NLO load to the server, and the NLO loaded from the server obtains a client identifier, The client identifier is NL
The NLO sends the NLO identifier issuance request to the server together with the NLO identifier,
When the work is performed by using the NLO,
A client device for presenting an NLO identifier and making a processing request to the server; and a client / server system for remote operation. 2. The server encrypts the NLO attached data and transmits the encrypted NLO attached data to the client device. The NLO loaded on the client device decrypts the encrypted NLO attached data and sends the encrypted NLO attached data together with a client identifier to the server. The client for remote operation according to claim 1, wherein the client sends an NLO identifier request to the client.
Server system. 3. The client / server system for remote operation according to claim 1, wherein said client identifier is an IP address. 4. An NLO is provided to a client device that operates using an NLO which is a program loaded and operated via a network only when necessary, and the provided NL is provided.
A server that performs a predetermined process according to a process request from the client device and receives the NLO request from the client device and permits the client device to load the NLO; Of the NLO requested to be loaded
Is transmitted to the client device together with the NLO attached data which is data generated differently each time the NLO is loaded, and the NL loaded in the client device is transmitted.
When a request for issuing the client identifier and the NLO attached data presenting the NLO attached data from O is received, the presented client identifier and the NLO attached data are attached to the client identifier obtained when the NLO request was received and the provided NLO. After confirming that the received NLO data matches the NLO attached data, an NLO identifier that is a different value for each provided NLO is issued, and the issued NLO identifier is transmitted to the client device that transmitted the NLO identifier issuance request. Receiving the processing request from the NLO, the NLO issued by the NLO identifier presented with the processing request
A server that performs the requested processing after confirming that it matches the identifier. 5. The server according to claim 4, wherein said client identifier is an IP address. 6. A client device that performs work using an NLO, which is a program loaded and operated via a network only when necessary, and an NL for the client device.
A server protection method in a client / server system for remote operation, comprising: a server for providing a predetermined processing according to a processing request from the provided NLO; Transmitting an NLO request to the server to perform the NLO request, and when the server receives the NLO request from the client device and permits the client device to load the NLO, the client device that has transmitted the NLO request is specified. Acquiring a client identifier for performing the load and transmitting the NLO requested to be loaded to the client device together with NLO attached data which is data generated differently each time the NLO is loaded; The loaded NLO is retained Gets the client identifier of the client device are, and sending the NLO identifier issuance request in the server the client identifier presented to the server along with the NLO attachments, NLO from NLO held in the client device
After the server that has received the identifier issuing request confirms that the presented client identifier and the NLO attached data match the client identifier obtained when the NLO request was received and the NLO attached data attached to the provided NLO, , NL which is a different value for each provided NLO
O, and issues the issued NLO identifier to the NL.
Transmitting an O identifier issuance request to the NLO that has transmitted the request; an NLO held in the client device presenting the NLO identifier to make a processing request to the server; and a server receiving the processing request from the NLO. Executing the requested processing after confirming that the NLO identifier presented together with the processing request matches the issued NLO identifier, in the remote operation client-server system. 7. The server encrypts the NLO attached data and transmits the encrypted NLO attached data to the client device. The NLO loaded on the client device decrypts the encrypted NLO attached data and sends the encrypted NLO attached data together with a client identifier to the server. 7. The remote operation client according to claim 6, wherein the client sends an NLO identifier request to the client.
A server protection method in a server system. 8. The server protection method in a remote operation client / server system according to claim 6, wherein the client identifier is an IP address.