JP2018060373A - Information processing device, information processing method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve operability of UI components by using an event acquisition function which is unable to be used by applications with general authority.SOLUTION: An information processing device comprises an operating environment in which applications may operate. A first application and a second application may operate in the operating environment, wherein the first application has authority to register a listener in the operating environment to notify an event due to a user operation outside of an area of components to the components constituting a screen, wherein the second application has no such authority, and the second application has a requesting means to request the listener registration for the first application when the components constituting the screen of the second application is the components requiring notification of the event due to the user operation outside the area of the components. The first application has a registration means to request, in response to the request from the second application, the listener registration in the operation environment.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an information processing apparatus, an information processing method, and a program.

  Conventionally, the security of software operating on devices has been important. However, there is an aspect in which convenience is lost when security is tightened. For example, for a graphical user interface, a pull-down component programmed with software operates in response to a user operation. A pull-down component with good operability can be realized by closing the pull-down component displayed on the screen in response to a touch operation outside its own area. On the other hand, there is a problem that if a pull-down component can acquire all user operations, a security hole may occur.

  In response to this problem, Patent Document 1 devises a mechanism in which only specific modules process user operations. In Patent Document 1, in an environment where two OSs operate on one device, a touch event on the screen is processed by only one of the two OSs. At this time, by concealing the processing of the touch event from another OS, an operation of intercepting and stealing the event is prevented. However, if event processing is completely concealed, it is not possible to deal with a case where an event is to be acquired for a legitimate purpose.

JP 2014-133504 A

  The present invention has been made in view of the above problems, and can restrict the authority of an application operating on the system and can acquire and respond to an event generated in the system by a UI component constituting the screen of the application. Like that.

  In order to solve the above problems, the present invention has the following configuration. That is, an information processing apparatus having an operating environment in which an application operates, and has an authority to register a listener for notifying a component constituting a screen of an event caused by a user operation outside the region of the component in the operating environment. A first application and a second application that does not have the authority operate in the operating environment, and the second application is configured such that a part constituting the screen of the second application is outside the area of the part. In the case of a component that requires notification of an event by a user operation, it has request means for requesting the first application to register the listener, and the first application is a request from the second application. And a registration means for requesting registration of the listener in the operating environment. .

  According to the present invention, a UI component that uses system functions can be used even in an application whose authority is restricted, and the convenience of the application is improved.

Schematic which shows an example of the hardware constitutions of information processing apparatus. The schematic diagram which shows an example of the software structure constructed | assembled on information processing apparatus. The schematic diagram which shows the structural example of the function with which the software which concerns on this invention is provided. The flowchart which shows the execution process of an application. The flowchart which shows UI component creation processing. The flowchart which shows an AWT event listener registration process. The flowchart which shows a process when a user touches a screen. The figure which shows the state which the pull-down of UI components opened and closed. The figure which shows the example of a description of an authority list. The flowchart of the calling process of the UI component listener registration means which concerns on 2nd Embodiment.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

<First Embodiment>
[System configuration]
(Hardware configuration)
FIG. 1 is a diagram illustrating an example of a hardware configuration of a general information processing apparatus 101 to which the present invention can be applied. The information processing apparatus 101 includes, as a hardware configuration, a CPU 11, an input device 12, a storage device 13, a display device 14, and an external connection IF, and each component is communicably connected via the bus 10.

  The CPU 11 realizes each function, flowchart, or the like described later by performing processing based on a program corresponding to each of an application, a program execution environment, and the like, which will be described later, stored in the storage device 13. The input device 12 corresponds to a keyboard or a mouse for inputting information. The storage device 13 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), a hard disk device, and the like, and stores data used in processing based on the program in addition to the above-described programs. The display device 14 is a display that displays a screen or the like. A touch panel display in which the input device 12 and the display device 14 are integrated may be used. The external connection IF 15 is a network interface or various connection interfaces with external devices.

  The CPU 11 can function as various means by executing a program. A control circuit such as an ASIC (Application Specific Integrated Circuit) that operates in cooperation with the CPU 11 may function as these means. These means may be realized by cooperation between the CPU 11 and a control circuit that controls the operation of the information processing apparatus 101. Further, the CPU 11 does not have to be a single one and may be a plurality. In this case, the plurality of CPUs 11 can perform processing in a distributed manner. Further, the plurality of CPUs 11 may be disposed on a single computer, or may be disposed on a plurality of physically different computers. Note that the means realized by the CPU 11 executing the program may be realized by a dedicated circuit.

(Software configuration)
FIG. 2 is a diagram illustrating an example of a software configuration of the information processing apparatus 101. In the information processing apparatus 101, an operating system (OS) 201, a virtual machine 202, an application framework 203, and various applications (system application 204, application 205) are configured in a hierarchical structure. The OS 201 is software that is the basis of the entire system. For example, an OS such as Linux (registered trademark) is an example of the OS 201. The virtual machine 202 is software that provides an operating environment in which an application operates on itself while being a process on the OS 201. An example of the virtual machine 202 is a Java (registered trademark) VM (Virtual Machine). The application framework 203 is a program that operates on the virtual machine 202 and is configured by intermediate code. The application framework 203 manages the life cycle of various applications.

  The system application 204 and the application 205 are applications that operate on the application framework 203. The system application 204 operates with system authority. On the other hand, the application 205 is executed with limited authority. In FIG. 3, two applications 205 are shown, but the present invention is not limited to this configuration, and more applications 205 may be operable.

  Next, a configuration for managing application authority on the system of the information processing apparatus 101 will be described. FIG. 3 is a diagram illustrating a part that controls a function related to authority and a function related to an event in the software configuration illustrated in FIG. 2. Each application has functions other than those shown in FIG. 3, and the description thereof is omitted because it is not directly related to the present invention.

  The virtual machine 202 includes event management means 301 and authority management means 302. The event management unit 301 manages an input to the information processing apparatus 101 as an event. Specific examples of the input include a touch operation by a user on the touch panel and a press of a hard key provided in the information processing apparatus 101. These inputs are managed by the event management unit 301 as touch events and hard key events. The input managed as an event is not limited to the above, and may be other operations such as various user operations via the input device 12 or the external connection IF 15, for example.

  The authority management unit 302 manages the authority of the application operating on the virtual machine 202. For example, when an application registers a listener in the event management unit 301 in order to acquire and process a touch event, the application has listener registration authority based on information managed by the authority management unit 302. It is confirmed whether or not. A listener (event listener) is an object that monitors an event and controls to execute a process associated with the event when some event occurs. The process here corresponds to a function or a method. Here, if anyone can acquire the event that causes the execution of the process, the operation of a malicious program such as a key logger stealing a password or password is allowed. Therefore, an unauthorized program (application) is controlled so that listener registration in the event management unit 301 cannot be performed. In other words, the authority management unit 302 of the virtual machine 202 manages the authority of each application, and confirms the authority of the requesting application when requesting registration of the listener.

  The application framework 203 includes FW authority management means 303. The intra-FW authority management unit 303 manages the authority of an application operating on the application framework 203. This makes it easy to define the format of the application authority list 307 in a format unique to the application framework 203 and to add a unique authority. Actual authority management is performed using authority management means 302 provided as a standard function of the virtual machine 202.

  The system application 204 includes a UI component listener registration unit 304 and a system authority list 305. The UI component listener registration unit 304 is one of the functions of the system application 204 and is used only from the UI component library 306 provided in the application 205. The system authority list 305 is a list of authorities that the system application 204 has. In the present embodiment, it is assumed that the system application 204 has a listenToAllAEVENTs authority to be described later. By having this authority, the system application 204 can register a listener for acquiring an event on the virtual machine 202 in the virtual machine 202.

  The application 205 includes a UI component library 306 and an application authority list 307. The UI component library 306 is a library used when the application 205 draws a screen on the display device 14 or the like. By using the UI component library 306 in which various UI components are defined in advance, the developer of the application 205 can easily use the components without knowing details. The application authority list 307 is a list of authorities that the application 205 has. In the present embodiment, it is assumed that the authority of the application 205 is limited as compared to the authority of the system application 204, and the application 205 does not have the listenToAllAEVENTs authority. Therefore, for example, the application 205 is restricted so that a listener that acquires an event of a user operation for a region other than the UI component area cannot be directly registered in the virtual machine 202.

  A description example of the application authority list 307 of the application 205 and the system authority list 305 of the system application 204 is shown in FIG. In FIG. 9, in the code 901, the environment variable user. The authority of reading (reading), writing (writing), executing (execute), and deleting (delete) for the files in the directory set as home is described, and these operations are permitted. In the code 902, the authority of acceptance (accept), connection (connect), standby (listen), and name resolution (resolve) at an arbitrary socket is described, and these operations are permitted.

  So far, the configuration of the information processing apparatus 101 has been described. In the present embodiment, the virtual machine 202 is assumed to be a Java virtual machine (Java VM), and the application framework 203 is assumed to be OSGi (Open Services Gateway initiative; registered trademark).

  In the present embodiment, a description will be given for the application 205 that uses a pull-down component included in the UI component library 306. An example of the pull-down component is shown in FIG. The pull-down component is a UI component that configures the screen, and includes a pull-down button 801 and a pull-down menu 802. When the area of the pull-down button 801 is touched, a pull-down menu 802 is displayed. When the area inside the pull-down button 801 or the area outside the pull-down button 801 is touched while the pull-down menu 802 is displayed, the pull-down button 801 returns to the closed state.

  Here, in order to return to the closed state of the pull-down menu 802, the pull-down button 801 needs to recognize that an event has occurred in which an area inside or outside the part is touched. However, depending on the implementation of the OS 201 and the virtual machine 202, an event in which an area outside the component is touched cannot be easily acquired. For example, in the implementation corresponding to the X-Window System that is common in the Unix-based OS, the components are processed as independent windows. In this case, each component is notified only of events within its own area. As a result, each component cannot recognize that an event has occurred where the outside of the component area has been touched.

  In order to acquire an event outside the area, it is necessary to register a listener in the event management unit 301 of the virtual machine 202. The listener registration process is performed by the UI component library 306, and the authority of the UI component library 306 is that of the application 205. That is, in the application authority list 307, it is necessary to describe the authority to register the listener in the event management unit 301. The authority to register a listener here is an authority defined by Java (registered trademark) as a standard, and is known as listenToAllAWEvents. Hereinafter, listener registration that requires listenToAllAWTEvents authority will be referred to as AWT event listener registration.

  On the other hand, if the listenToAllAWTEvents right is given to the application 205, a malicious operation is enabled by the right. Therefore, there is a need for a method in which the UI component library 306 can register an AWT event listener while restricting the authority of the application 205. Therefore, in this embodiment, the system application 204 that operates with the same system authority as that of the virtual machine 202 is linked to the UI component library 306. Here, for convenience, the system application 204 is also referred to as a “first application”, and the application 205 is also referred to as a “second application”.

[Processing flow]
The operation of the information processing apparatus 101 will be described with reference to FIGS. FIG. 4 is a flowchart showing application execution processing. FIG. 5 is a flowchart illustrating processing for creating a UI component. FIG. 6 is a flowchart showing registration processing of an AWT event listener. Both processes are realized by the CPU 11 of the information processing apparatus 101 reading and executing a program stored in the storage device 13 or the like.

  The flow of processing for executing the application 205 will be described with reference to FIG. When the execution of the application 205 is started, this processing flow is started.

  In S 401, the application framework 203 acquires the application authority list 307 of the started application 205 using the intra-FW authority management unit 303.

  In step S <b> 402, the application framework 203 registers the authority of the application 205 in the authority management unit 302 of the virtual machine 202.

  In step S <b> 403, the application 205 creates a UI component using the UI component library 306 in order to display a screen. At this time, the application 205 only creates a UI component using the function of the UI component library 306, and details of creation processing such as listener registration are hidden from the application 205. Details of this processing step will be described with reference to FIG. Then, this processing flow ends.

  Next, details of the UI component creation processing in S403 in FIG. 4 will be described with reference to FIG. UI parts created by the UI part library 306 include pull-down parts, label parts, button parts, text input parts, and the like, but are not limited thereto. For example, a plurality of types of label parts having different appearances are prepared for the label parts. Which UI component is to be created follows the instructions of the application 205.

  In step S501, the UI component library 306 creates an instance of the specified UI component.

  In step S502, the UI component library 306 confirms whether the created UI component is a component that reacts to an event. For example, if the created UI component is a label component, only characters and images are displayed, and there is no need to react to an event. On the other hand, in the case of a button component, it is a UI component that reacts to an event in order to perform a linked process at the same time it changes to a drawing indicating that it has been selected when it is touched. Information regarding whether or not the UI component reacts to an event is defined in advance, and the information is retained. If it is a UI part that reacts to an event (YES in S502), the process proceeds to S503. If it is a UI part that does not react to an event (NO in S502), the process flow ends.

  In step S <b> 503, the UI component library 306 requests the virtual machine 202 to register a listener to know events in the area of the UI component itself. No special authority is required for registering listeners to get events in their area. Accordingly, here, the virtual machine 202 registers a listener in response to a request from the UI component library 306. The listener registration here may be requested (called) via the UI component listener registration unit 304 of the system application 204 or may be directly requested (called) to the virtual machine 202.

  In step S504, the UI component library 306 confirms whether the created UI component is a UI component that reacts to an event outside its own area. For example, a pull-down component is a UI component that reacts to an event outside its own area. Here, it is assumed that whether or not the UI component responds to an event outside its own area is defined in advance and that information is held. If it is a UI part that reacts to an event outside its own area (YES in S504), the process proceeds to S505. If it is not a UI part that reacts to an event outside its own area (NO in S504), this process flow ends. To do.

  In step S505, the UI component library 306 performs AWT event listener registration processing. Details of this processing will be described with reference to FIG. Then, this processing flow ends.

  Next, details of the AWT event listener registration process in S505 of FIG. 5 will be described with reference to FIG.

  In step S601, the UI component library 306 confirms whether or not there is a predetermined operating environment in which an event outside the component area can be acquired. For example, when the information processing apparatus 101 has a unique window system, or in the case of a Windows (registered trademark) virtual machine 202, an operating environment (specification) in which an event outside the component area can be acquired. On the other hand, the mounting corresponding to the general X-Window System in the Unix-based OS becomes an operating environment in which events outside the component area cannot be acquired. Information on the operating environment here is stored in advance, and determination may be made based on this information. If an event outside the UI component area cannot be acquired (NO in S601), the process proceeds to S602, and if it is an environment in which an event outside the component area can be acquired (YES in S601), the process flow ends.

  In step S602, the UI component library 306 calls the UI component listener registration unit 304 of the system application 204 and requests registration of a listener for acquiring an event outside the UI component area.

  In step S <b> 603, the UI component listener registration unit 304 calls the listener registration function of the virtual machine 202 in response to a request from the UI component library 306 of the application 205 and requests listener registration. This registration function is an API (Application Programming Interface) that the virtual machine 202 includes as a standard.

  In step S604, the virtual machine 202 confirms whether or not the application that has requested registration has the authority for listener registration. As described above, the UI component listener registration unit 304 of the system application 204 operates as the system application 204 and has a listener registration authority.

  In step S605, the virtual machine 202 determines whether the application that requested registration of the listener has the authority. If the user has authority (YES in S605), the process proceeds to S606. If the user does not have authority (NO in S605), the process proceeds to S607.

  In S606, the virtual machine 202 registers the AWT event listener in the event management unit 301. Then, this processing flow ends.

  In step S607, the virtual machine 202 performs exception processing without registering the requested listener. Then, this processing flow ends. As long as the registration of the listener is requested from the UI component library 306 via the UI component listener registration unit 304 as shown in FIG. 6, the case where it is determined in S605 that there is no registration authority does not occur. However, when the application 205 directly calls the listener registration function of the virtual machine 202 in order to register a listener for an event related to the outside of the UI component area, the exception processing is performed without registering because there is no listener registration authority. .

  Hereinafter, processing when a user touches a touch panel, which is one of the input devices 12 included in the information processing apparatus 101, will be described with reference to FIG. This process is realized by the CPU 11 of the information processing apparatus 101 reading and executing a program stored in the storage device 13 or the like.

  In step S <b> 701, the information processing apparatus 101 receives a screen touch operation by the user via the input unit.

  By the touch operation, an input is notified to the virtual machine 202 via the OS 201, and in step S702, the event management unit 301 generates a touch event.

  In step S <b> 703, the virtual machine 202 confirms whether the coordinates of the touch event are within the area of the UI component being displayed on the screen. If it is within the UI part area (YES in S703), the process proceeds to S704. If it is outside the UI part area (NO in S703), the process proceeds to S705. When a plurality of UI parts are included in one screen, it may be determined whether or not the coordinates of the touch event are within the region for each UI part.

  In step S704, the virtual machine 202 notifies the event to the listener of the UI component in which the touch event is performed in the area. Along with this, processing associated with the UI component is executed.

  In S705, the virtual machine 202 notifies the event to the AWT listener. That is, it is notified that a touch event has occurred outside its own area. Accordingly, for example, in the case of a pull-down component as shown in FIG. 8, an operation of closing the pull-down menu 802 is executed. Then, this processing flow ends.

  In the above description, the pull-down component is described as an example. However, the present invention is not limited to this, and other UI components may be targeted. In addition, the touch operation has been described as an example of the user operation, but the present invention is not limited to this, and may be another user operation such as pressing a key button or a flick operation.

  As described above, the method by which the UI component library 306 can register the AWT event listener while restricting the authority of the application 205 has been described. According to the present embodiment, it is possible to improve the convenience of the application while restricting the authority of the application to prevent malicious operations.

<Second Embodiment>
In the first embodiment, the mechanism for calling the UI component listener registration unit 304 of the system application 204 from the UI component library 306 of the application 205 when registering the AWT listener has been described. At this time, it is assumed that the developer of the application 205 does not know the existence of the UI component listener registration unit 304 included in the system application 204. That is, the UI component listener registration unit 304 has a private configuration. However, if a malicious developer is informed of the presence of the UI component listener registration unit 304, there is a risk that the UI component listener registration unit 304 may be used by an attack program.

  Therefore, in the present embodiment, a method of confirming the caller inside the UI component listener registration unit 304 and rejecting other than the call from the UI component library 306 will be described. In other words, the UI component listener registration unit 304 requests the virtual machine 202 to register the listener if the request source for registration of the AWT event listener is the UI component library.

  FIG. 10 is a flowchart of processing in which the UI component listener registration unit 304 of the system application 204 confirms the caller. Here, a case where the UI component listener registration unit 304 is called in S602 of FIG. 6 described in the first embodiment will be described as an example.

  When called from the UI part library 306 of the application 205, in step S1001, the UI part listener registration unit 304 acquires the stack at that time. The stack here is a stack of function calls as a frame. By scanning the stack from above, it is possible to confirm via which function the UI component listener registration unit 304 is called.

  In step S <b> 1002, the UI component listener registration unit 304 acquires a frame that is currently stacked one level below the stack. When the UI component listener registration unit 304 is properly called, the next lower frame becomes a specific function of the UI component library 306. The specific function is, for example, a pull-down component creation function. Here, as in the first embodiment, a pull-down component will be described as an example. However, if it is a UI component other than this, it becomes a creation function of the UI component. Here, it is assumed that the specific function of the UI component library 306 is defined in advance and that information is managed.

  In step S <b> 1003, the UI component listener registration unit 304 confirms whether the acquired frame is the UI component library 306. If the frame is the UI parts library 306 (YES in S1003), the process proceeds to S603 in FIG. 6, and if the frame is not the UI parts library 306 (NO in S1003), the process proceeds to S1004. Since the processing after S603 is the same as the processing described in the first embodiment, description thereof is omitted.

  In step S1004, the UI component listener registration unit 304 performs exception processing without performing registration processing. Then, this processing flow ends. In this case, the processing after S603 in FIG. 6 is omitted.

  In this embodiment, the case where the UI component listener registration unit 304 is called in S602 in FIG. 6 has been described as an example. However, when the UI component listener registration unit 304 is called in another route (other than the UI component library 306). This processing is also performed. At this time, if the UI component listener registration unit 304 is called from another route (other than the UI component library 306), the listener is not registered and exception processing is performed.

  According to the present embodiment, in addition to the effects of the first embodiment, it is possible to further improve the security.

<Other embodiments>
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

202 ... Virtual machine, 203 ... Application framework, 204 ... System application, 301 ... Event management unit, 302 ... Authority management unit, 303 ... Authority management unit in FW, 304 ... UI component listener registration unit, 306 ... UI component library

Claims (8)

An information processing apparatus having an operating environment in which an application operates,
A first application having the authority to register in the operating environment a listener for notifying an event by a user operation outside the region of the component to a component constituting the screen;
A second application not having the authority;
Operates in the operating environment,
The second application is configured such that when a component constituting the screen of the second application is a component that requires an event notification by a user operation outside the region of the component, the listener's Having request means for requesting registration;
The information processing apparatus according to claim 1, wherein the first application includes registration means for requesting registration of the listener in the operating environment in response to a request from the second application. The operating environment is
A management means for managing information about application permissions;
When receiving a request for registration of the listener, it is determined whether the request source of the request has authority to register the listener based on information managed by the management unit, The information processing apparatus according to claim 1, further comprising: a control unit that controls whether or not to register the listener based on a determination result. The second application includes means for determining whether or not the operating environment is a predetermined operating environment that is a specification for notifying an event by a user operation outside a region of the component to a component constituting the screen. In addition,
The information processing apparatus according to claim 1, wherein the request unit requests the first application to register the listener when it is determined that the operating environment is not the predetermined operating environment. apparatus. The first application further includes confirmation means for confirming a request source of the request when receiving a request for registration of the listener,
The requesting unit makes a request for registration of the listener to the operating environment when the requesting unit confirms that the request source is the requesting unit of the second application. Item 4. The information processing device according to any one of Items 1 to 3.   The information processing apparatus according to any one of claims 1 to 4, wherein a component that requires notification of an event by a user operation outside the area is a pull-down component. The operating environment is an operating environment by a Java virtual machine,
The information processing apparatus according to claim 1, wherein the listener is an AWT event listener. A method for controlling an information processing apparatus including an operating environment in which an application operates,
A first application having the authority to register in the operating environment a listener for notifying an event by a user operation outside the region of the component to a component constituting the screen;
A second application not having the authority;
Operates in the operating environment,
In the second application, when the component constituting the screen of the second application is a component that requires notification of an event by a user operation outside the region of the component, the listener's Has a request process to request registration;
The information processing apparatus control method according to claim 1, further comprising: a registration step of requesting registration of the listener in the operating environment in response to a request from the second application. To a computer with an operating environment where the application runs
A first application having the authority to register in the operating environment a listener for notifying an event by a user operation outside the region of the component to a component constituting the screen;
A second application not having the authority;
In the operating environment,
In the second application, when the component constituting the screen of the second application is a component that requires notification of an event by a user operation outside the region of the component, the listener's Function as a request means to request registration,
A program that causes the first application to function as a registration unit that makes a request for registration of the listener in the operating environment in response to a request from the second application.

Images