JP4128982B2 - Information processing apparatus, information processing method, computer program, and storage medium - Google Patents

Description

  The present invention relates to a technique for permitting / not permitting execution of a general application program that operates on a general-purpose information processing apparatus such as a personal computer.

  In recent years, the importance of security has increased, and a number of security mechanisms have been considered in various fields. In particular, a security mechanism based on authentication is widely used. For example, a security mechanism based on authentication is used as a mechanism that is used only by a legitimate user when logging in to a terminal or system, such as when an operating system (hereinafter referred to as OS) of a computer terminal is started or when logging into a Web system. ing.

  A mechanism for applying a security function to the activation of an application program installed in a computer terminal is considered.

  In order to achieve such an object, a technique is known in which user authentication is performed for installation and activation of an application, and the application is not activated unless the authentication process is performed (Patent Document 1).

In the system of this technique, it is possible to provide security for activation of an application by authentication and further simplify authentication for a plurality of applications.
JP 2001-236315 A

  However, the authentication security function in the system using the above technology is only for a specific application program determined in advance, and the authentication security function cannot be added later to an existing application that does not require authentication.

It is an object of the present invention to provide a mechanism for preventing security of an application by authentication and preventing an executable application program from being operated from another client device on a network.

In order to achieve the above object, an information processing apparatus of the present invention comprises the following arrangement. That is,
An information processing apparatus capable of executing an application program,
Conversion means for encrypting the application program and converting the application program into an encrypted format;
User information receiving means for receiving input of user information for authenticating the user of the application program;
Authentication means for performing authentication processing of the user according to the user information received by the user information receiving means;
Decryption means for decrypting the encrypted application program converted by the conversion means into an executable application program;
Determination means for determining whether or not the storage destination of the application program generated by being decrypted by the decryption means is a shared folder,
When the authentication unit authenticates the user and the determination unit determines that the storage destination of the application program is not a shared folder, the decryption unit is executed, while the determination unit executes the application program. When the storage location is determined to be a shared folder, or when the user is not authenticated by the authentication unit, execution of the decryption unit is prohibited.

ADVANTAGE OF THE INVENTION According to this invention, while providing the security with respect to an application by authentication, the mechanism which prevents operating the application program of an executable format from the other client apparatus on a network can be provided.

  Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

<First Embodiment>
FIG. 1 is a diagram showing a configuration of a security management apparatus having a security management program for executing security management of an application program according to an embodiment of the present invention.

  The security management apparatus according to the embodiment will be described using an example using a personal computer (hereinafter, PC) 100 which is a general-purpose information processing apparatus shown in the figure. Further, as an OS (operating system) operating on the PC 100, Windows (registered trademark) provided by Microsoft Corporation in the United States is taken as an example.

  The CPU 101 comprehensively controls each device and controller connected to the system bus 104. The ROM 102 stores a BIOS (Basic Input Output System) and a boot program. The RAM 103 functions as a main memory, work area, and the like for the CPU 101.

  An external memory (usually a hard disk drive) 111 stores an OS and various application programs (word processors, spreadsheets, etc., regardless of the type) 112. These application programs 112 include at least the execution program 113 (exe file) that is the parent program. In addition, the security management program 114 serving as the center in the embodiment is also stored in the external memory. Furthermore, the external memory 111 also stores data files created by various applications.

  When the apparatus is turned on, the CPU 101 executes the boot program in the ROM 102 to access the external memory 111 via the memory controller 107 and load the OS into the RAM 103. Then, display processing of an OS operation screen on the CRT 110 via the video controller 106 and input processing from a pointing device (KB / PD) 109 (instruction means) such as a keyboard and a mouse (registered trademark) via the input controller 105 The application program 112 and the security management program 114 in the embodiment are activated by accessing the external memory 111 as necessary. In some cases, communication with a network is performed via the communication interface 108.

  It should be noted that FIG. 1 is an example of an apparatus in the embodiment. That is, the display device is not limited to a CRT, and may be a liquid crystal display device, and the external memory 111 is not limited to a hard disk and may be of any type.

<Outline of security management program>
The security management program 114 in the embodiment adds a security function to the application program 112, but is configured by two independent programs.

  One is a file conversion program that converts an existing general application program into an inexecutable format file, and the other is an authentication processing program that performs activation and user maintenance processing for the application program file converted into an inexecutable format. .

  The “file conversion program” is a program that can be executed only by the administrator, that is, only by an administrator who has undergone a preset administrator authentication process. For this reason, when this file conversion program is installed on the PC 100 or when it is first started up, the administrator name and password are entered from the keyboard, encrypted and stored (registered) in an appropriate location in the external memory. When starting next time, the user is prompted to enter the password, and the file conversion process can only be entered if it matches the password registered as an administrator. That is, the file conversion program itself includes an authentication process, and further improves the security function.

  First, it is assumed that the administrator activates the file conversion program and succeeds in authentication. The administrator designates an application program file to be permitted to be executed only by a specific user among application programs installed on the PC 100 (regardless of the type of general application other than the OS-related program). To do. Any designation method may be used. For example, the full path of the corresponding application program from the keyboard, for example, “c: \ aaa \ bbb \ ccc.exe” (a further directory (folder) “aaa” in the drive c) Enter the character string of the executable program file named “ccc.exe” that exists in the directory “bbb”. Alternatively, a method may be used in which a file browser format window is displayed, and the target execution program is specified in the order of drive and subfolder in accordance with the operation of the pointing device.

  In any case, when the target application program file “ccc.exe” is designated and given instructions are given, the file conversion program of the embodiment converts it into a format that cannot be executed without going through the authentication processing program (details will be described later). ), And the converted file name is “ccc.ex_”, and a predetermined folder managed by the security management program in the embodiment (in this embodiment, the path of the management folder is “c: \ Ovl \ bin \”). And delete the original program file “ccc.exe”. At this time, by setting the visible / invisible information of the file attribute (generally called an attribute) of the converted file “ccc.ex_” to “invisible”, the file does not seem to exist in the external memory 111 in appearance. Pretend to. As a result of the above, the application program file “ccc.exe” does not actually exist, and the existence of the converted file “ccc.ex_” can be provided without special operation. .

  Hereinafter, a file that cannot be executed or opened by the file conversion program unless the authentication program in the embodiment is used is referred to as a scrambled file.

  On the other hand, the application activation part (excluding the maintenance process here) in the authentication program roughly includes four processes. The first is authentication processing. The second is restoration processing for restoring the executable file “ccc.exe” from the scramble file “ccc.ex_” when the authentication is successful. The third is application activation processing that requests the OS to activate the restored “ccc.exe”. A fourth process is a deletion process in which after the application program “ccc.exe” is requested to end, the “ccc.exe” is deleted after waiting for the “ccc.exe” to end.

  As a result, the period during which the application program file “ccc.exe” is present in the external memory 111 is substantially limited to the execution of the application, and the executable application program file “ccc. It is possible to suppress duplication of “exe”. Hereinafter, the present embodiment will be described more specifically.

  In the following description, it is assumed that the security management program 114 in the embodiment is already installed in the external memory.

<Description of file conversion processing program>
First, the processing of the file conversion program constituting the security management program 114 in the embodiment will be described with reference to the flowchart of FIG. Here, the execution file 113 of the application to which a security function is to be added is converted into a scramble file that cannot be started directly from the OS. Each step described below is realized by the CPU 101 executing a security management program loaded in the RAM 103.

  First, when the user starts the file conversion process of the security management program, the CPU 101 controls the video controller 106 to check whether or not the user is an administrator, and a user interface for inputting the administrator name and password. A (window) drawing instruction is issued, and a key input is awaited (step S310). In the following, the process of making a drawing request to the video controller 106 is simply referred to as “display”.

  In step S311, the process proceeds to step S301 only when the result of key input matches the administrator name and password registered in advance. Note that this process may be terminated when the number of errors in the entered administrator name and password is greater than or equal to a predetermined number.

  When the process proceeds to step S301, a user interface (hereinafter, UI) of the input screen shown in FIG. 4 is displayed.

  In step S302, the user selects and inputs an execution file of an application program to be designated as a conversion process target using a keyboard or a pointing device. As described above, the character string of the file name with the path that specifies the location of the target application program file is input to the text box 41 by operating the keyboard as described above, or “file designation” in FIG. The cursor linked to the pointing device is moved to the position of the button 42, a button provided on the pointing device is pressed, a file viewer window (not shown) is displayed, and the drive, directory, and file name are similarly operated. When the file is designated, a character string including the path information of the file is displayed in the text box 41. In addition, since the technique itself which selects a file with a file viewer is well-known, description here is abbreviate | omitted.

  Next, in step S303, the CPU 101 determines whether or not the file selection input in step S302 has been made. If the selection input has been made, a display for enabling the “file conversion” button 43 that is grayed out in FIG. (Step S304, FIG. 5). If no selection input has been made, the process returns to step S301 to display the UI shown in FIG.

  In step S305, the CPU 101 determines whether the file conversion button 43 has been pressed. If the result of determination in step S305 is that the file conversion button has been pressed, in step S306, the designated file (the file at the path position input in the text box, in the case shown in FIG. ("FcPro.exe" file in it) is converted. The details of step S306 will be described later. As a result, the scrambled file “FCPro.ex_” (extension “exe” indicating an executable file) is underlined in the management folder (c: \ Ovl \ bin \). (Replaced file) will be created.

  In step S307, it is determined whether the file conversion has been completed normally. This is to deal with some kind of error (for example, when writing fails due to insufficient capacity, etc.) while creating a file. If the process ends abnormally, the process returns to step S304 to prompt the user to press the file conversion button again.

  If it is determined that the conversion process has been completed normally, the original file (“FcPro.exe” in FIG. 4) of the conversion source is deleted in step S308, and this process ends.

  Next, details of the processing in step S306 will be described with reference to FIG. As described above, the scramble file has a format that cannot be executed as it is. When actually executing (starting up), reverse conversion processing into an executable file is involved. Therefore, it is desirable that conversion and reverse conversion be fast without stress.

  Therefore, in step S306 in the present embodiment, conversion to a scramble file is performed as follows.

  First, in step S601, the CPU 101 opens a writing file having a different extension character string of the original execution program file in the management folder, and writes dummy data in the first 1024 bytes (1 KB).

  Normally, when the OS executes a program file, it analyzes and executes the header. The dummy data to be written is data that causes an error when analyzed. The reason is that if dummy data is not written and a file with the extension “ex_” is manually set to “exe” and executed, it may run out of control. In the above case, since the execution is disabled in the two stages of the extension and the file header (which can be said to be the third stage because it is set invisible as described later), the safety is improved.

  In step S602, the file size of the file conversion target file (application execution file) input by the user in step S302 is acquired. This can be obtained by calling a function that the OS normally has.

  In step S603, the CPU 101 reads data from the execution file 113 into the RAM 103 in units of a predetermined amount. This “predetermined amount” in the embodiment is 1024 bytes (= 1 KB).

  In step S604, the CPU 101 divides the 1024-byte data on the RAM 103 into two by 512 bytes, which is a half of the data. In step S605, the divided data are rearranged in a predetermined order and written in the file secured in the external memory 111.

  In the embodiment, since it is divided into two, 512 bytes in the latter half are written, and then 512 bytes in the first half are written. FIG. 7 shows a specific example of the processing in steps S601 to S605 described above.

  In step S606, the CPU 101 determines whether the data size that has not yet been read is 1024 bytes or less from the file size of the executable file 113 and the data capacity that has already been read. Continue. If the remaining data size is 1024 bytes or less, the process proceeds to step S607, where the remaining data is read into the RAM 103 and written into the converted file on the external memory 111 (step S608).

  Although the conversion process is completed as described above, in the embodiment, for safety, the attribute of the hidden file is set as the file attribute of the scramble file (xxx.ex_) generated as the write file in step S609.

<Description of security management in authentication program>
As described above, the administrator stores the scramble file generated from the necessary application program file in the management folder, but the number of files is not limited.

  On the other hand, in order to restore and execute, the reverse processing described above is performed, but preparing the programs for restoring the same number of scrambled files consumes the external memory 11. It's not efficient.

  Some application programs are conditional on starting from a path location that originally existed.

  Therefore, in the embodiment, a common authentication program for executing restoration processing is used for a plurality of scramble files (application program files converted to be unexecutable). However, since the location and arguments of each non-executable application program file are different, we dealt with creating a shortcut file for each application. A shortcut file is not a substance file of an application but is composed of location information of the application program file and a character string as an argument, and has a very small file size.

For example, the authentication program (including the restoration program) file in the embodiment is
c: \ Ovl \ Bin \ PWExec.exe
If so, create a shortcut file with the following description format.
c: \ Ovl \ Bin \ PWExec.exe "{original program name with path}""c: \ Ovl \ Bin \ {scrambled file name}"
For example, the file name with the path where the application program file originally existed is
c: \ Fcraft \ FCXEdtr.exe
If so, create a shortcut file containing the following description:
c: \ Ovl \ Bin \ PWExec.exe "c: \ Fcraft \ FCXEdtr.exe""c: \ Ovl \ Bin \ FCXEdtr.ex_"
When this shortcut file is placed on the desktop screen or registered in the menu, for example, when the user inputs an execution instruction, the authentication program “c: \ Ovl \ Bin \ PWExec.exe” is started. Then, the argument “c: \ Fcraft \ FCXEdtr.exe c: \ Ovl \ Bin \ FCXEdtr.ex_” is delivered to the authentication program.

  Therefore, when the authentication program is started, authentication (determination process of whether or not the password set by the administrator and the password input by the user matches) is first performed, and if the authentication is successful, it is the second argument. The scrambled file “c: \ Ovl \ Bin \ FCXEdtr.ex_” is reverse converted to create the original executable file “c: \ Fcraft \ FCXEdtr.exe” as the first argument, and then reverse converted. The obtained “c: \ Fcraft \ FCXEdtr.exe” should be started.

  The authentication program “c: \ Ovl \ Bin \ PWExec.exe” continues to reside in the RAM 103 even after launching the target application. When the corresponding application terminates, the executable file is deleted and its own file is deleted. Processing is also terminated.

  Although a shortcut file is created, in the case of the embodiment, since the OS running on the PC 100 is Windows (registered trademark), the OS function is used. FIG. 2 shows an example of a shortcut creation GUI prepared in the OS. It can be created by describing the above character string in the “command line” text box in the figure (three examples are shown in the figure). In the embodiment, an example in which a shortcut file is used has been described. However, the same applies to a batch file, and it can easily be realized that other OSs can be realized in the same manner. In the case of a batch file, it can be created by a text editor, and it is also adopted by many OSs.

  Now, the authentication program ("c: \ Ovl \ Bin \ PWExec.exe" file in the above example) file in the embodiment is processed by the administrator as a process other than the reverse conversion of the scrambled file into an executable file. It is assumed that maintenance processing such as setting is also performed. The maintenance process can be shifted only when the administrator code and the administrator password are input. In particular, when the administrator performs a maintenance operation, the authentication program may be directly started instead of the shortcut.

  Based on the above, the processing procedure of the authentication program in the embodiment will be described according to the flowchart of FIG.

Here,
c: \ Ovl \ Bin \ PWExec.exe "c: \ test \ AAA.exe""c: \ Ovl \ Bin \ AAA.ex_"
A description will be given of an example in which an icon of a shortcut file in which the character string is written is activated by operating a pointing device (usually double-clicking). In other words, the program file “c: \ test \ AAA.ex_” converted to non-executable is reverse-converted to be executable and started.

  When the authentication program in the present embodiment is activated, in step S801, the CPU 101 displays the user interface 90 shown in FIG. 9 using the display data stored in the external memory 111, and the user name (user ID) is displayed in the text boxes 91 and 92. ) And password prompting. In the upper part of the displayed user interface, a message character string of the name of a file to be executed (a file that does not exist at this time but is reversely converted) is displayed. In the above example, a message to start “c: \ test \ AAA.exe” will be displayed.

  In step S802, the process waits for input of a user name (user ID) and a password character string from the keyboard 109.

  Next, in steps S803, S804, and S811, the CPU 101 waits for any one of the “start” button 93, the “maintenance” button 94, and the “end” button 95 to be pressed (clicked).

  If it is determined in step S803 that the “start” button has been pressed, the CPU 101 performs authentication identification processing in step S805. If it is determined in step S804 that the “maintenance” button has been pressed, authentication identification processing is performed in step S806.

  Here, in the processing of step S805 and step S806, a table for pairing the user ID and password set and registered in advance by the administrator is created, and authentication is performed with reference to the table. The table is stored in the external memory 111 as a file (hereinafter referred to as an authentication table file), but it is assumed that a predetermined encryption process is performed to ensure security. In addition to the user ID and password, the table stores authority information (whether it is an administrator or a general user) and information related to various types of maintenance as one record. There is no limit to the number of registered users (number of records).

  When the “start” button 93 and the “maintenance” button 94 are pressed, the encryption of the authentication table file is decrypted. In step S805, authentication processing is performed based on whether or not information in which the user ID input in the text boxes 91 and 92 and the character string of the password completely match is present in the decrypted authentication table file (administrator). Or general users). In step S806, the user ID indicating the administrator and the password are collated as authority information of the authentication table file. In other words, only the administrator can enter the maintenance process when the “maintenance” button 94 is pressed. In addition, since the encryption process and the encryption / decryption process itself are well-known, the detail is abbreviate | omitted.

  It goes without saying that the password entered in the authentication table file is encrypted, the input password is encrypted by a predetermined method, and the encrypted data can be compared and authenticated.

  If authentication fails in steps S805 and S867, the process proceeds to step S807, and it is determined whether the number of consecutive failures has reached a predetermined number (5 in the embodiment). When the predetermined number of times is reached, the process proceeds to step S808, the account is locked and the user ID cannot be used. In step S809, an error is displayed on the CRT 110, and this process ends.

  If it is determined in step S805 that the authentication has succeeded, the process advances to step S810, and the CPU 101 performs a rearrangement execution process that is a substance of a security management process described later.

  If it is determined in step S806 that the authentication is successful, the process proceeds to step S811, and a maintenance process described later is performed.

  Next, the rearrangement execution process of step S810 will be described using the flowchart of FIG. This is a process of generating an executable application program file from the scramble file and starting it. More specifically, from the file "c: \ Ovl \ bin \ AAA.ex_" with the invisible attribute set, create an executable file "c: \ test \ AAA.exe" temporarily and launch it And monitoring.

  First, in step S1001, an argument when the authentication program in the embodiment is activated is analyzed and acquired. In this example, the string of two arguments "c: \ test \ AAA.exe" (executable file name with path) and "c: \ Ovl \ bin \ AAA.ex_" (scrambled file name with path) Will get.

  Next, in step S1002, the CPU 101 determines whether the path of the acquired character string with the extension “exe” (in this case, “c: \ test”) is set as a shared folder on the network on the PC 100. Check for no. Whether or not the folder is a shared folder can be checked by acquiring a shared information key from a registry managed by the OS.

  If it is determined that the shared folder is set, an error is displayed in step S1003, and data indicating the error occurrence and its type is output to an audit log (not shown) in step S1011.

  If the path of the extension "exe" is set to a shared folder, the reason for error handling is that if it is restored from a scrambled file to an executable file, it can be executed from another client device on the network even if it is temporary This is because there is a possibility that the existence of the file becomes unknown and there is a risk of being copied to a malicious user.

  If it is determined that the path of the extension “exe” is not set in the shared folder, the process advances to step S1004 to execute the EXE file restoration process (details will be described later). As a result, an executable file is generated in “c: \ test \ AAA.exe”, and the process advances to step S1005 to request the OS to execute the file and start it. As a result, at least an application program having “c: \ test \ AAA.exe” as a parent is read into the RAM 103, and various operations using the application can be performed. The execution file activation request may be executed using the OS function CreateProcess ().

  In step S1006, the CPU 101 additionally writes the user ID, activation time, and activation application name in the audit log file.

  As a result, since the activated application resides in the RAM 103, the CPU 101 monitors the application execution process (whether “AAA.exe” is resident in the RAM) in steps S1007 and S1008. Monitoring of the execution process can be realized by monitoring the state of the process from the process ID returned by the OS in the operation such as application activation. When the process of the application program in question is completed, that is, when the user ends the application “AAA.exe”, the process proceeds to step S1008, and the restored application program file “c: \ test \ AAA.exe” is stored. In step S1010, the application end timing is additionally output to the audit log, and the process ends.

  Normally, an application program being executed is protected by the OS and cannot be deleted. By using this, a request for deleting an executable file being executed periodically (for example, at intervals of 5 seconds) may be sent to the OS, and the processing in step S1010 may be performed when the deletion is successful. In this case, there is a possibility that the application program file will be deleted at a stage slightly delayed from the timing when the application program is actually terminated, but it can be kept to a few seconds at most. Equivalent to deleting.

  Next, the EXE file restoration process in step S1004 will be described with reference to the flowchart of FIG. This process is also an inverse conversion process of the file conversion process by recombination described with reference to FIGS.

  Here, the character strings of two arguments “c: \ test \ AAA.exe” (executable file name with path) and “c: \ Ovl \ bin \ AAA.ex_” (scrambled file name with path) are already given. Please note that it is.

  First, in step S1101, the file size of the scrambled file “c: \ test \ AAA.ex_” is obtained from the file property information, and a writing file named “c: \ test \ AAA.exe” is opened (reserved) )

  In step S1102, a predetermined number of bytes of data are skipped from the beginning of the scrambled file, and the process proceeds to step S1103 (in the embodiment, the predetermined number of bytes is set to 1024 bytes).

  In step S <b> 1103, the CPU 101 reads a predetermined amount (for example, 1024 bytes) of data into the RAM 103 from the skipped data. In step S1004, the CPU 101 divides the read data by a predetermined amount (512 bytes in the embodiment). In this example, it is divided into two.

  Write the predetermined amount (512 bytes) of the divided data to the file “c: \ test \ AAA.exe” opened for writing, and then the predetermined amount (512 bytes) of the first half Writing is performed (step S1105).

  The processing of steps S1103 to 1105 is repeated until the amount of unread data of the conversion source “c: \ Ovl \ bin \ AAA.ex_” becomes 1024 bytes or less in step S1106.

  If the remaining amount is less than or equal to the predetermined amount in step S1106, the remaining data is read to the RAM 103 (step S1107), the read data is written to a file opened for writing, the file is closed, and this process is performed. finish.

<Maintenance processing>
Next, the maintenance process in the embodiment will be described. This process is performed when the administrator inputs his / her user ID and password and presses the “maintenance button” 94 in the UI of FIG.

  This maintenance process is to maintain the user ID, password, and authority information of each user. User additions, deletions, password changes, and user authority settings are made, and various settings are made using the input screen shown in FIGS. These pieces of information are used as information used for the authentication processing in steps S805 and S806 and the audit log.

  FIG. 12 shows an initial UI 120 for maintenance processing. The contents of the authentication table file displayed in the upper area 121 are the user name, authority information, and password. It is possible to determine which user is an administrator (authorization item “super” = maintenance processing is possible) and is a general user.

  When the displayed user name is selected, the following two items can be set for the user. One is a usage period in the display area 122 (indefinite in the case of 0), and the second is a countermeasure when input errors are repeated ten times or more as shown in the display area 123. FIG. 8 shows an example in which 5 times is set in step S807. In the embodiment, it is possible to select from three measures: no countermeasure, a message indicating that reception is stopped when a user ID is input, and ignore (no processing is performed).

  In FIG. 12, when the “Add” button in the area 121 is pressed, the user name field on the input screen in FIG. 13 is displayed in a blank state, and a new user name, password, authority can be set and registered. Is possible. When the “delete / change” button is pressed, editing can be performed for the user selected in the area 121. FIG. 12 shows that the user name “BBB” is in the selected state. When the “delete / change” button is pressed in this state, the user name and password are changed or managed as shown in FIG. It is possible to make changes such as granting the authority of a person. When the “delete” button is pressed, information regarding the user name is deleted, and the process returns to FIG. If the “SET” button is pressed, the contents of change are provisionally determined and the processing returns to FIG.

  When the “end setting” button in FIG. 12 is pressed, a process of finally reflecting the maintenance operation in the authentication table file is performed, and this process ends. When the “Cancel” button is pressed, the previous work is discarded and the authentication table file is not changed.

  In the above-described embodiment, the example in which the original application program file is rearranged for each predetermined amount as the algorithm for generating the scramble file has been described. However, the executable file may be generated by encrypting the executable file. However, in general, encryption processing (and encryption / decryption processing) requires complicated operations, and the load on the CPU is large. Therefore, it takes a time that cannot be ignored before converting into an executable file. In this respect, when recombination is performed for each predetermined amount as in the above-described embodiment, it is preferable that the scramble and its release processing are simple, and the application can be started within a time without a sense of incongruity.

  In addition, a file conversion program that converts an existing general application program into an inexecutable format file and an authentication processing program that performs startup and user maintenance processing for an application program file that has been converted into an inexecutable format can be executed independently. Instead of the above program, it may be provided in the form of a partial program that realizes each function as one security management program. In this case, it is needless to say that the operator needs to select whether to execute the file conversion function or the authentication processing function on a selection screen (not shown) when the security management program is started.

<Second Embodiment>
The above embodiment relates to security management of application program files. Therefore, the data file created after the authentication is successful and the application is started can be freely viewed and edited if the corresponding application can be executed on another PC. Therefore, in the second embodiment, an example will be described in which a data file created by an application program is also scrambled to be a file that cannot be opened from another PC.

In order to simplify the description, it is assumed that the path of an application program file to which security is to be added and a data file to which the application program can be edited and security is to be added are as follows.
Application program file: "c: \ Test \ aaa.exe"
Data file: “d: \ data \ xxx.dat”

Using these file conversion programs described in the first embodiment, the following two files with security added are generated, and the original two files are deleted.
Application program file after security is added: "c: \ Ovl \ Bin \ aaa.ex_"
Data file after adding security: “c: \ Ovl \ Bin \ xxx.da_”

  Since there are two scrambled files to be created, it is necessary to distinguish between them. In the embodiment, the application program is distinguished by adding the character string “-p” option and the data file by adding the character string “-o” option.

Therefore, in the above case, when creating a shortcut file including the following character string, the following character string is input (the authentication program is the same as in the first embodiment “c: \ Ovl \ Bin \ PWExec .exe ").
c: \ Ovl \ Bin \ PWExec.exe "-pc: \ Test \ aaa.exe""c: \ Ovl \ Bin \ aaa.ex_""-od: \ data \ xxx.dat""c: \ Ovl \ Bin \ xxx.da_ "
That is, the authentication program “c: \ Ovl \ Bin \ PWExec.exe” makes it possible to identify four arguments. Here, the first and second arguments are handled in the same manner as in the first embodiment. The third and fourth argument character strings describe the data file after security release and the scrambled data file with security added.

When the authentication program “c: \ Ovl \ Bin \ PWExec.exe” acquires four character strings including the above options, the following processing is performed (provided that authentication is successful).
Step 1. Generate "c: \ Test \ aaa.exe" (executable application program) from the scramble file "c: \ Test \ aaa.ex_" according to the "-p" option.
Step 2. Generate "d: \ data \ xxx.dat" (data file that can be read and written by application) from scrambled file "d: \ data \ xxx.da_" according to "-o" option.
Step 3. An executable application program is started by giving a character string with a path of a data file that can be read and written by the application as an argument.
Step 4. Monitors whether the application program ("aaa.exe" in the above case) has terminated.
Step 5. When the application program ends, the application program file “c: \ Test \ aaa.exe” is deleted from the external memory 111.
Step 6. “D: \ data \ xxx.da_” is created from the updated data file “d: \ data \ xxx.dat” using the file conversion program of the embodiment. At this time, the file with the same name that existed before editing is overwritten.
Step 7. The file “d: \ data \ xxx.dat” is deleted from the external memory 111.

  Note that the process of step 5 may be performed after step 6 or in step 7. Further, if the shared folder includes the executable file and editable file path positions after descrambling, the descrambling is not canceled as in the first embodiment.

  Further, the file conversion program and the user ID & password authentication process are the same as those in the first embodiment, and the process replacing step S810 in FIG. 8 will be described with reference to the flowchart in FIG. In the following description, DFLAG is a flag for determining whether or not to restore a scrambled data file, and is cleared to “0” and secured in the RAM when this process is started. Is.

  First, in step S1401, an argument when the authentication program is executed is analyzed. As described above, the argument can include an executable program file name with a path that starts with the "-p" option and its scrambled file name, a data file name with a path that starts with the "-o" option, and its scrambled file name. .

  In step S1402, whether or not a data file option exists is determined based on the presence or absence of “−o” described above. If it is determined that there is a data file option, the process advances to step S1421, and it is determined whether or not the path position of the data file name of the conversion destination is included in the shared folder.

  If it is determined that the conversion destination path is included in the shared folder, an error is displayed in step S1403, and error information to that effect is written in the audit log file in step S1404.

  If it is determined that the data file conversion destination is not a shared folder, the process advances to step S1405 to set “1” in the flag DFLAG.

  On the other hand, if it is determined in step S1402 that there is no data file option, or if the process of step S1405 is performed, the CPU 101 performs the process of step S1406. Here, it is determined whether or not an application program file option exists in the argument based on the presence or absence of “-p”. If the application program file option does not exist, an error is displayed in step S1407, and error information is written in the audit log in step S1408.

  If it is determined in step S1406 that there is an application program file option, the process proceeds to step S1409. Here, it is determined whether or not the flag DFLAG is “1”.

  If DFLAG is “0”, the scramble data file is not specified and only the activation of the application program is set, and the process advances to step S1411. On the other hand, if DFLAG is “1”, it indicates that the application to be restored needs to be restored to a readable / writable data file, so the data file is restored in step S1410 and the process proceeds to step S1411. .

  When the process proceeds to step S1411, an application program restoration process is performed. As a result, at least an executable application program file is generated, and when there is a data file option, a restored data file is generated. In step S1412, the restored data file name ( The OS is requested to start the restoration application program with a path). Note that when the flag DFLAG = 0, the restoration data file name is blank, and as a result, the application alone is activated, which is the same as in the first embodiment.

  Thereafter, in step S1413, a message indicating that the application has been started is written in the audit log, and in steps S1414 and S1415, it is monitored that the application that has been requested to start is finished.

  If it is determined that the activated application program has ended, the process advances to step S1416 to delete the restored application program file. In step S1417, if the flag DFLAG is “1”, the edited original data file (data file indicated by the file name with the conversion destination path specified by the data file option) is scrambled. Data conversion processing is performed in step S1418, and the original data file is deleted in step S1419. In step S1420, the fact that the application has ended and, if the data file has been edited, are written to the audit log file, and this processing is ended.

  As described above, according to the second embodiment, in addition to the operational effects of the first embodiment, the security of the data file can be ensured while being a data file created by a general application. Is also possible.

<Third Embodiment>
In the first embodiment, it is necessary to input an authentication program, a scrambled file name with path, and a restored program file name with path from the keyboard.

  Some application programs have predetermined paths in which the program file must exist, and some of the application programs do not allow an error in the input of a character string indicating the path location of the restoration destination.

  Therefore, in the third embodiment, an example will be described in which at least the input of the restoration destination path position can be omitted.

  As shown in FIG. 5, when the file name with path of the application program to be converted is determined, the file name described in the text box at that time is utilized.

  As shown in FIG. 15, the first 1024 bytes of the scrambled file have the same meaning as that of FIG. The difference is that the character string described in the text box 41 of FIG. 5 is added to the next 1024 bytes (though it is not limited to this size, as long as it has sufficient capacity to describe the path). The code indicating the appropriate end mark may be stored at the end. Further, the character string may be encrypted and stored.

  As a result, the file size of the scrambled file is 2048 (2K) bytes larger than the original application program file, but it slightly increases considering that the size of the current application is several hundred KB and sometimes several MB. Just do it.

In addition, the character string described in the shortcut in the third embodiment is
c: \ Ovl \ Bin \ PWExec.exe "c: \ Ovl \ Bin \ {scrambled file name}"
It becomes.

  Along with this, the authentication program “c: \ Ovl \ Bin \ PWExec.exe” has a process to acquire the executable file name with the restoration destination path from the 1025th byte onward from the beginning of the scrambled file passed as an argument. No explanation will be necessary.

<Fourth Embodiment>
An example developed further from the third embodiment will be described as a fourth embodiment.

  In the fourth embodiment, an authentication program “c: \ Ovl \ Bin \ PWExec.exe” is operated. However, instead of operating the original authentication program “c: \ Ovl \ Bin \ PWExec.exe”, the copy is operated.

  FIG. 16 shows a memory map of the authentication program “c: \ Ovl \ Bin \ PWExec.exe” in the fourth embodiment. A reserved area for storing an appropriate character string is prepared at the rear end (not necessarily the rear end). Then, after step S609 in FIG. 6, the process in FIG. 17 is performed.

  In step S610, the file name with path for storing the execution program is input. The path and file name may be arbitrarily determined by the administrator. The path may be entered with a keyboard, but the operation can be easily performed by specifying a desired drive and folder using a file browser and finally entering a file name such as “xyz.exe”. This is exactly the same as entering the file name to be saved when data is newly created by the application program.

  In step S611, the authentication program “c: \ Ovl \ Bin \ PWExec.exe” is copied as the specified file name (“xyz.exe” in the above example). At this stage, the file “xyz.exe” and the original file “PWExec.exe” have the same contents except for the file names.

  In step S612, the path name of the general application program file selected by the administrator and the character string of the scrambled file name with path (encrypted) are stored in the reserved area of the copy destination program file “xyz.exe”. Stored).

  “PWExec.exe” (the same applies to xyz.exe) in the fourth embodiment operates as follows.

  When it starts, it performs authentication processing, and if the authentication is successful, if there is a significant character string in its reserved area, the stored scrambled file name with path, general application program file name with path The executable file is restored from the scramble file. The rest is the same as in the first embodiment.

  Further, according to the fourth embodiment, it is possible to include the data file name with a path shown in the second embodiment.

  Although the first to fourth embodiments according to the present invention have been described above, the main part of the present invention is configured by a computer program. Usually, a computer program is stored in a computer-readable storage medium such as a CDROM, and can be executed by setting it in a computer and copying or installing it in a system. Of course, such a computer-readable storage medium is also within the scope of the present invention. Is clearly included.

  In the embodiment, the authentication program includes processing for restoring and executing a scramble program file and processing for maintenance, but these may be independent. In particular, in the case of the fourth embodiment, since the authentication program is larger than the shortcut file, in order to reduce the size of the created execution program (copy of the authentication program), the program related to maintenance is excluded. Is desirable.

It is a block block diagram of the apparatus in embodiment. It is a figure which shows the example of the display screen during shortcut creation. It is a flowchart which shows the process sequence of the file conversion program in embodiment. It is a figure which shows the initial window of a file conversion program. It is a figure which shows the window at the time of designating the application program file in FIG. It is a flowchart which shows the detail of the file conversion process in FIG. It is a figure for demonstrating the concept of file conversion. It is a flowchart which shows the process sequence of the authentication program in embodiment. It is a figure which shows the example of the authentication window displayed at the time of starting of an authentication program. It is a flowchart which shows the detail of the rearrangement execution process in FIG. FIG. 11 is a flowchart showing details of EXE file restoration processing of FIG. 10. FIG. It is a figure which shows the window of a maintenance setting. It is a figure which shows the window displayed when performing a user's setting / change. It is a flowchart which shows the detail of the recombination execution process in FIG. 8 in 2nd Embodiment. It is a figure for demonstrating the concept of the file conversion in 3rd Embodiment. It is a figure which shows the memory map of the authentication program in 4th Embodiment. It is a flowchart which shows the process sequence added to FIG. 6 in 4th Embodiment.

Claims (8)

An information processing apparatus capable of executing an application program,
Conversion means for encrypting the application program and converting the application program into an encrypted format;
User information receiving means for receiving input of user information for authenticating the user of the application program;
Authentication means for performing authentication processing of the user according to the user information received by the user information receiving means;
Decryption means for decrypting the encrypted application program converted by the conversion means into an executable application program;
Determination means for determining whether or not the storage destination of the application program generated by being decrypted by the decryption means is a shared folder,
When the authentication unit authenticates the user and the determination unit determines that the storage destination of the application program is not a shared folder, the decryption unit is executed, while the determination unit executes the application program. An information processing apparatus that prohibits execution of the decryption means when it is determined that the storage location is a shared folder, or when the user is not authenticated by the authentication means. Monitoring means for monitoring execution of an executable application program decrypted by the decrypting means;
A data conversion means for converting the data file into an encrypted format by encrypting the data file created by the application program when the monitoring means determines that the application program is terminated;
Data decrypting means for decrypting the encrypted data file converted by the data converting means into a data file in a format executable by the application program;
Data determination means for determining whether or not the storage destination of the data file generated by being decrypted by the data decryption means is a shared folder;
When the user is authenticated by the authentication means, and when the data determination means determines that the storage destination of the data file is not a shared folder, the data decryption means is executed, while the data determination The execution of the data decryption unit is prohibited when the storage unit determines that the storage location of the data file is a shared folder or when the user is not authenticated by the authentication unit. The information processing apparatus described in 1. A data deletion unit that requests the operating system to delete the corresponding data file before encryption when the data file is converted into an encrypted format by the data conversion unit. Item 3. The information processing device according to Item 2. When the executable application program is converted into the encrypted format by the conversion means, the program further comprises program deletion means for requesting an operating system to delete the application program before encryption. The information processing apparatus according to any one of claims 1 to 3. 5. A deletion means for requesting an operating system to delete the executable application program decoded by the decoding means when the execution of the executable application program is completed. The information processing apparatus according to any one of the above. In an information processing method in an information processing apparatus capable of executing an application program,
A converting step in which the converting means of the information processing apparatus encrypts the application program and converts the application program into an encrypted format;
A user information accepting step for accepting an input of user information for authenticating a user of the application program;
An authentication step in which the authentication unit of the information processing apparatus performs an authentication process of the user according to the user information received in the user information reception step;
A decryption step of decrypting the encrypted application program converted by the conversion step into an executable application program;
The determination unit of the information processing apparatus includes a determination step of determining whether a storage destination of the application program generated by being decrypted in the decryption step is a shared folder,
When the user is authenticated in the authentication step, and when it is determined in the determination step that the storage destination of the application program is not a shared folder, the decryption step is executed, while in the determination step An information processing method for prohibiting execution of the decryption step when it is determined that a storage destination of an application program is a shared folder, or when the user is not authenticated by the authentication step. A computer program that causes a computer to function as an information processing apparatus capable of executing an application program by being read and executed by the computer,
Conversion means for encrypting the application program and converting the application program into an encrypted format;
User information receiving means for receiving input of user information for authenticating the user of the application program;
Authentication means for performing authentication processing of the user according to the user information received by the user information receiving means;
Decryption means for decrypting the encrypted application program converted by the conversion means into an executable application program;
Function as a determination unit that determines whether the storage destination of the application program generated by being decoded by the decoding unit is a shared folder,
When the authentication unit authenticates the user and the determination unit determines that the storage destination of the application program is not a shared folder, the decryption unit is executed, while the determination unit executes the application program. A computer program that prohibits execution of the decryption means when it is determined that the storage location is a shared folder, or when the user is not authenticated by the authentication means. A computer-readable recording medium on which the computer program according to claim 7 is recorded.

Images