JP5617734B2 - File management method, file management apparatus, and file management program - Google Patents

Description

  The present invention relates to a file management method, a file management apparatus, and a file management program.

  Conventionally, for the purpose of preventing leakage of confidential information or the like that can be included in data handled by an application program, it has been studied to manage the status of an application program between a protected state and an unprotected state (for example, Patent Document 1). ).

  That is, a process that handles a file protected by encryption or the like (hereinafter referred to as a “protected state file”) is set to a protected state. On the other hand, a process that handles such an unprotected file (hereinafter referred to as “unprotected” file) is set to an unprotected state. At the time of writing to the file by the protected process, the written content is encrypted. Therefore, even if the user does not give an instruction for encryption, the written content is automatically encrypted and protected.

  On the other hand, there is an application program that can simultaneously edit a plurality of files in one process. That is, the application program displays a plurality of windows in one window and displays different files in each window.

  With respect to such an application program, it is desirable that a process in which a protected state file and an unprotected state file are mixedly displayed or edited is set to a protected state. This is because it is possible to prevent information leakage due to the content written in the protection state file being stored without being encrypted.

JP-A-10-161935 JP 2007-26105 A

  However, if a protected state file and a non-protected state file are mixed and displayed or edited in the protected state, writing to the non-protected state file is encrypted and overwritten. Will be. As a result, the unprotected state file becomes a protected state file against the user's intention. Here, the file that has been changed from the unprotected state file to the protected state file is hereinafter referred to as “file A”.

  Such a situation impairs the convenience of the file A. For example, there is a possibility that the file A cannot be opened in a system environment where management between the protected state and the unprotected state is not performed. This is because the file A is encrypted.

  Further, it is assumed that the file A is an application program setting file. That is, the file accessed by the application program is not limited to the file that is directly operated by the user. The setting file for defining the behavior of the application program is also an access target.

  Generally, the setting file is often read when an application program process is started. Then, if the file A becomes a protection state file, an application program that is not scheduled to be the protection state file may not be normally started. Even if the application program can be activated, all processes activated thereafter are protected. As a result, there is a problem that an application program that uses the file A as a setting file cannot be used in an unprotected state. In this case, the convenience is remarkably deteriorated, for example, the unprotected state file cannot be created.

  Accordingly, it is an object of the present invention to provide a file management method, a file management apparatus, and a file management program that can improve convenience related to file protection.

  Therefore, in order to solve the above-described problem, the file management method includes a procedure for receiving a request for opening a first file and a request for opening the received first file, with respect to a startup unit of a file operation program capable of operating a plurality of files. A procedure for determining whether a predetermined identifier is included in the path name specified in the request, and, if the predetermined identifier is included in the path name, the first file according to the predetermined identifier A procedure for selecting a protection state file or a non-protection state file as an object to be opened, and when the path identifier does not include the predetermined identifier, when the protection state file is not opened with respect to the activation unit, Select the unprotected status file of the first file as the target to open, and the protected status file is When open, the procedure for selecting the protection status file of the first file as an open target and the procedure for opening the protection status file or the non-protection status file of the first file selected as the opening target The computer executes.

  Convenience regarding file protection can be improved.

It is a figure which shows the hardware structural example of the file management apparatus in embodiment of this invention. It is a figure which shows the software structural example of the file management apparatus in 1st embodiment. It is a flowchart for demonstrating an example of the process sequence of a file open process. It is a figure which shows the structural example of a file information storage part. It is a flowchart for demonstrating an example of the process sequence of the conversion process from a logical path name to a physical path name. It is a figure which shows the structural example of the forward conversion table which a conversion rule memory | storage part memorize | stores. It is a flowchart for demonstrating an example of the process sequence of the write-in process to a file. It is a flowchart for demonstrating an example of the process sequence at the time of acquisition of the list | wrist of a logical path name. It is a figure which shows the structural example of the reverse conversion table which a conversion rule memory | storage part memorize | stores. It is a figure which shows the software structural example of the file management apparatus in 2nd embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a hardware configuration example of a file management apparatus according to an embodiment of the present invention. The file management apparatus 10 in FIG. 1 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, a display device 106, an input device 107, and the like that are mutually connected by a bus B.

  A program for realizing processing in the file management apparatus 10 is provided by the recording medium 101. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program need not be installed from the recording medium 101 and may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 realizes functions related to the file management apparatus 10 in accordance with a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network. The display device 106 displays a GUI (Graphical User Interface) or the like by a program. The input device 107 is a keyboard, a mouse, or the like, and is used for inputting various operation instructions.

  An example of the recording medium 101 is a portable recording medium such as a CD-ROM, a DVD disk, or a USB memory. An example of the auxiliary storage device 102 is an HDD (Hard Disk Drive) or a flash memory. Both the recording medium 101 and the auxiliary storage device 102 correspond to computer-readable recording media.

  FIG. 2 is a diagram illustrating a software configuration example of the file management apparatus according to the first embodiment.

  In FIG. 1, a file management apparatus 10 includes one or more applications 11 and a file system 12.

  The application 11 is an example of a file operation program that operates a file in the present embodiment. The application 11 operates a plurality of files for each activation unit or execution unit (hereinafter, unified as “activation unit”). The activation unit is a unit for each memory space generated by loading an execution file or the like of the application 11 into the memory device 103 according to activation or execution of the application 11 such as a process or a thread. The file operated by the application 11 is not limited to a file generated as a product (hereinafter referred to as “product file”). For example, a file in which setting information related to the behavior of the application 11 is recorded, such as a setting file. The deliverable file is a file output by the original function of the application 11. For example, in the case of word processing software, a document file corresponds to a product and a file. Therefore, the fact that the application 11 operates a plurality of files for each activation unit is not necessarily limited to that the activation unit can operate a plurality of deliverable files.

  The file system 12 is a so-called file system provided by an OS (Operating System). That is, the file system 12 provides a function for systematically managing data recorded in the auxiliary storage device 102 using the concept of files and directories (or folders). The file system 12 is shared by a plurality of applications 11.

  In the present embodiment, the file system 12 includes a file management unit 13, an unprotected state file storage unit 14, a protected state file storage unit 15, and the like.

  The protection state file storage unit 15 stores (stores) the protection state file using the auxiliary storage device 102. A protected state file is a file that has been put into a protected state. The protection state refers to a state in which content reference is restricted or a predetermined operation is restricted by, for example, encryption, password assignment, or operation restriction.

  The unprotected state file storage unit 14 stores (stores) the unprotected state file using the auxiliary storage device 102. An unprotected file is a file that is not protected. The protected state and the non-protected state are in a relative relationship. That is, for example, the unprotected state file may also be encrypted or may be given a password. In this case, the protection state file may be encrypted by a stronger encryption method, for example, or the protection state file may be given a password of a longer character string, for example.

  In this embodiment, for convenience, an encrypted file is a specific example of a protected state file, and a plain text file is a specific example of an unprotected state file.

  The file management unit 13 executes various operations related to files requested by the application 11. The various operations include, for example, file generation, opening, reading, and writing. In the present embodiment, acquisition of a list of file path names (hereinafter simply referred to as “path names”) is also included in various operations relating to files. In the figure, the file management unit 13 includes an open processing unit 131, a write processing unit 132, a list response unit 133, a state management unit 134, a file information storage unit 135, a conversion unit 136, a conversion rule storage unit 137, and the like.

  The open processing unit 131 controls file open processing. The write processing unit 132 controls file write processing. The list response unit 133 responds with a list of path names of files belonging to a certain directory (or folder) in the file system 12. The file information storage unit 135 stores information regarding the opened file. The file information storage unit 135 can be realized using, for example, a storage device connected to the auxiliary storage device 102 or the file management device 10 via a network.

  The entity of the file that is the target of the open process or the entity of the file that is the target of the write process depends on whether the operation mode of the application 11 is the protection mode or the non-protection mode. Can be different. Specifically, in this embodiment, two entities, a protected state file and an unprotected state file, can be managed simultaneously for one file. That is, the “one file” in the above refers to a logical file (hereinafter referred to as “logical file”), not a physical file. On the other hand, “substance” refers to a physical file. Therefore, in this embodiment, two physical files, a protected state file and an unprotected state file, can be managed simultaneously for one logical file. The logical file is basically a file recognized by software (application 11 in the present embodiment) belonging to a layer higher than the file management unit 13 or a user. The physical file is a file recognized by the file system 12.

  Management of two physical files for one logical file is realized, for example, by making the path names of both physical files different. As a first example of the difference in path name, the file names of the two physical files are the same, and the directories of the unprotected state file and the protected state file are different. For example, the protected state file may be stored in a directory named “protected” under the directory of the unprotected state file. In this case, the directory of the unprotected state file corresponds to the unprotected state file storage unit 14, and the directory of the protected state file corresponds to the protected state file storage unit 15.

  A second example of the path name difference is to make the file names of two physical files different. For example, an extension indicating a protection state is given to the protection state file. In this case, the directory of the protected state file and the non-protected state file may not necessarily be different. Therefore, in this case, the storage area in which the unprotected state file is stored corresponds to the unprotected state file storage unit 14, and the storage area in which the protected state file is stored corresponds to the protected state file storage unit 15.

  In the present embodiment, the second example is adopted for convenience. That is, “.enc” is added to the protection state file as an extension. For example, when the file name of the unprotected state file is “a.doc”, the file name of the protected state file for the unprotected state file is “a.doc.enc”. However, the extension of both the protection state file and the non-protection state file may be the same, and a predetermined character string may be added to the portion other than the extension of the file name of the protection state file.

  The state management unit 134 manages the operation mode of the application 11 (a protection mode and a non-protection mode) for each activation unit of the application 11.

  The protection mode refers to a state in which one or more protection state files are included (open) in the operation target. The written contents in the protection mode are saved in a protected state (encrypted). The unprotected mode refers to a state in which the protected state file is not included in the operation target (not opened). The contents written in the unprotected mode are stored in the unprotected state (in plain text). It is desirable that the activation unit that has once transited to the protection mode does not return to the non-protection mode. Specifically, even if the protection status file is not opened at the present time, it is desirable that the activation unit in which the protection status file has been opened in the past is set to the protection mode. Even if the protection status file is not open at the present time, if the protection status file has been opened in the past, the contents of the protection status file may remain in the memory space (for example, the clipboard) of the activation unit. High nature. This is because in such a state, if the transition to the unprotected mode is permitted, the content of the protected state file (that is, the content to be protected) may be stored in the unprotected state. Therefore, in the present embodiment, the transition from the protection mode to the non-protection mode is not performed. However, if the safety is ensured, for example, the contents of the protection state file are deleted from the memory space in accordance with the switching of the operation mode, the transition from the protection mode to the non-protection mode may be performed. Good. In this case, a startup unit that does not include a protected state file as an operation target at the present time may be set to a non-protected mode.

  The conversion unit 136 converts a logical file path name (hereinafter referred to as “logical path name”) into a physical file path name (hereinafter referred to as “physical path name”). The conversion unit 136 outputs both the physical path name of the protected state file (protected physical path name) and the physical path name of the unprotected state file (unprotected physical path name) as the conversion result. The conversion unit 136 also determines which physical path name is given priority as an operation target, and outputs the determination result. That is, the conversion unit 136 also has a function of selecting a physical file to be operated according to whether it is a protected mode or a non-protected mode. The conversion unit 136 also performs conversion from a physical path name to a logical path name.

  The conversion unit 136 is used, for example, for the open processing unit 131 to specify a physical file to be opened. That is, in the open processing unit 131, a logical path name is specified as identification information to be opened. The open processing unit 131 acquires the physical path name for the logical path name using the conversion unit 136. The open processing unit 131 specifies the acquired physical path name in the file system 12 and opens the physical file corresponding to the specified logical path name. Also, the conversion unit 136 is used by the list information acquisition unit 133 to acquire logical path names to be included in the list. That is, the list response unit 133 acquires a list of physical path names from the file system 12. The list response unit 133 acquires a logical path name corresponding to the physical path name using the conversion unit 136. The list response unit 133 outputs a list of acquired logical path names to the application 11, for example.

  The conversion rule storage unit 137 stores a conversion rule between a logical path name and a physical path name. The conversion rule storage unit 137 can be realized by using, for example, a storage device connected to the auxiliary storage device 102 or the file management device 10 via a network.

  The file management unit 13 may include a processing unit related to file generation or reading. However, the description thereof is omitted in the present embodiment.

  When the file management unit 13 is incorporated into the existing file system 12, for example, the file management unit 13 may be implemented as a filter driver. The filter driver can receive the request before the request for the file system 12 reaches the request destination. Therefore, the filter driver can dynamically expand processing related to file operations such as file opening, writing, or list information acquisition.

  Hereinafter, the processing procedure of the file management apparatus 10 will be described. FIG. 3 is a flowchart for explaining an example of the processing procedure of the file opening process. In the following description, “application 11” means one activation unit of the application 11.

  In step S <b> 101, the open processing unit 131 of the file management unit 13 receives a file open request from the application 11. The file open request specifies the logical path name of the logical file to be opened, the open mode, and the like. The open mode is a parameter indicating whether the purpose of opening the file is to read (r) the file or write (w) to the file. You can also combine reading and writing. Note that an open mode indicating file generation also exists, but the open mode is excluded with respect to FIG.

  Subsequently, the open processing unit 131 causes the conversion unit 136 to perform conversion to a physical path name for the logical path name designated as the open target (S102). Specifically, the open processing unit 131 designates the logical path name and requests the conversion unit 136 to convert it to a physical path name. In response to the request, the conversion unit 136 converts the logical file into both a protected physical path name and an unprotected physical path name, and returns the conversion result. In the process of conversion, the conversion unit 136 determines whether a physical file is prioritized as a target to be opened, either a protected state file or an unprotected state file. The conversion unit 136 returns the conversion result so that the physical file to be prioritized can be identified from the open processing unit 131. For example, the interface of the conversion unit 136 accepts a logical path name in the first argument, outputs a protected physical path name and an unprotected physical path name by the second argument and the third argument, and is a physical file that is prioritized by the return value A value indicating (hereinafter referred to as “priority file”) is returned. The conversion unit 136 returns an error when there is no physical file corresponding to both of the two physical path names after conversion.

  When there is no physical file corresponding to the converted physical path name (No in S103), that is, when an error is returned from the conversion unit 136, the open processing unit 131 returns an error to the application 11 (S104). ), The process of FIG. 3 is terminated.

  On the other hand, if there is a physical file corresponding to the converted physical path name (Yes in S103) and the protection status file is a priority file (Yes in S105), the open processing unit 131 indicates that the application 11 is in the protection mode. It is determined whether or not there is (S106). Whether or not the protection mode is set can be determined by inquiring the state management unit 134.

  For example, the state management unit 134 uses the memory device 103 to manage a set of identifiers (for example, process IDs) of the applications 11 that are running in the protection mode (hereinafter referred to as “protection mode application list”). The open processing unit 131 specifies the process ID of the application 11 that is the file open request source, and inquires about the state (mode) of the application 11 related to the process ID. If the identifier related to the inquiry is included in the protection mode application list, the state management unit 134 makes a response indicating the protection mode. If the identifier related to the inquiry is not included in the protected mode application list, the state management unit 134 makes a response indicating the non-protected mode. The open processing unit 131 can obtain the process ID of the application 11 that is the file open request source by inquiring of the OS. Since the open processing unit 131 operates on the same process as the application 11, the process ID of the application 11 can be acquired by inquiring the OS of the process ID of the process in which the open processing unit 131 operates.

  If the application 11 is not in the protection mode (No in S106), the open processing unit 131 inquires of the user whether or not the transition to the protection mode is permitted (shift) (S107). For example, the open processing unit 131 causes the display device 106 to display a dialog for selecting permission / prohibition of transition to the protection mode. That is, when the mode is changed to the protection mode, a restriction is imposed that the subsequent writing to the file is performed on the protection state file storage unit 15. Therefore, by allowing the user to select or specify permission / inhibition of the transition, it is possible to avoid a transition to the protection mode that the user does not intend. The permission from the user does not necessarily have to be input interactively. For example, whether or not automatic transition to the protection mode is permitted may be specified in a setting file or the like. When the transition to the protection mode is permitted by the user (Yes in S108), the process proceeds to step S109. When the transition to the protection mode is not permitted by the user (No in S108), the open processing unit 131 returns an error to the application 11 (S104).

  When the application 11 is in the protection mode (Yes in S106), the process proceeds to step S109 without executing steps S107 and S108.

  In step S109, the open processing unit 131 causes the file system 12 to open a protected state file that is a priority file (S109). As the path name to be opened, the protected physical path name obtained in step S102 is designated. As a result of opening, a file descriptor (or a file descriptor or a file handle) is returned from the file system 12.

  Subsequently, the open processing unit 131 specifies the process ID of the activation unit of the application 11 that is the open request source, and notifies the state management unit 134 that the activation unit has entered the protection mode (S110). In response to the notification, the state management unit 134 adds the process to the protection mode application list. When the process ID is already included in the protection mode application list, the state management unit 134 ignores the notification.

  Subsequently, the open processing unit 131 associates the file identifier, status (protected or unprotected status), physical path name, and the like of the opened file and records them in the file information storage unit 135 (S111).

  FIG. 4 is a diagram illustrating a configuration example of the file information storage unit. The file information storage unit 135 shown in the figure stores a file identifier, a state, an unprotected physical path name, a protected physical path name, and the like for each opened file. In step S111 after step S110, the file identifier obtained in step S109, the value indicating the protection state, and the unprotected physical path name and protected physical path name obtained in step S102 are stored in the file information storage unit 135. To be recorded.

  On the other hand, if there is a physical file corresponding to the converted physical path name (Yes in S103) and the non-protected state file is a priority file (No in S105), the open processing unit 131 indicates that the application 11 is in protected mode. It is determined whether or not (S112).

  When the application 11 is in the protection mode (Yes in S112), the open processing unit 131 determines whether or not the open mode is read only (ReadOnly) (S113). If the open mode is read only (Yes in S113), the open processing unit 131 causes the file system 12 to open an unprotected state file that is a priority file (S114). As the path name to be opened, the unprotected physical path name obtained in step S102 is designated.

  If the open mode is read only, writing to the unprotected state file does not occur. Therefore, even in the protection mode, the unprotected state file is not set to the protected state. Therefore, if the open mode is read only, the unprotected file can be opened even in the protected mode.

  Subsequently, the open processing unit 131 associates the file identifier, state, physical path name, and the like of the opened file and records them in the file information storage unit 135 (S111). In step S111 after step S114, the file identifier obtained in step S114, the value indicating the unprotected state, and the unprotected physical path name and protected physical path name obtained in step S102 are the file information storage unit 135. To be recorded.

  On the other hand, when the open mode is not only reading (No in S113), the open processing unit 131 generates a copy (copy) of the unprotected state file related to the unprotected physical path name obtained in Step S102 (S115). The copy destination physical path name is the protected physical path name obtained in step S102 together with the unprotected physical path name. Since the copy destination physical file is a protection state file, the open processing unit 131 sets the copy destination physical file to the protection state. The protection state means that encryption is performed in the present embodiment. Subsequently, the open processing unit 131 causes the file system 12 to open the copy destination protection state file (S116).

  Subsequently, the open processing unit 131 associates the file identifier, state, physical path name, and the like of the opened file and records them in the file information storage unit 135 (S111). In step S111 after step S116, the file identifier obtained in step S116, the value indicating the protection state, and the unprotected physical path name and protected physical path name obtained in step S102 are stored in the file information storage unit 135. To be recorded.

  It should be noted that by opening the copy of the unprotected state file in the protected state, it is possible to prevent the unprotected state file from being put into the protected state against the intention of the user. In other words, even if writing occurs to an opened physical file (protected state file), there is no influence (execution of encryption, etc.) on the non-protected state file of the copy source.

  As described above, in the open process according to the present embodiment, when the protection unit file is selected as an open target by the conversion unit 136 (that is, when it is determined that it is a priority file), the logic designated as the open target is selected. The protection state file corresponding to the path name is opened. On the other hand, when the conversion unit 136 selects an unprotected state file as an open target (that is, when it is determined to be a priority file), an unprotected state file corresponding to the logical path name specified as the open target is selected. Opened. When the open mode is read only, the protection state file is opened, but the protection state file is copied from the non-protection state file file. Therefore, it can be said that the content of the unprotected state file is substantially opened.

  That is, in FIG. 3, the physical file selected by the conversion unit 136 is a target to be opened.

  Next, details of step S102 will be described. FIG. 5 is a flowchart for explaining an example of a processing procedure of conversion processing from a logical path name to a physical path name.

  When receiving the conversion request in which the logical path name is designated (S151), the conversion unit 136 refers to the conversion rule storage unit 137 and converts the logical path name into an unprotected physical path name and a protected physical path name ( S152).

  FIG. 6 is a diagram illustrating a configuration example of a forward conversion table stored in the conversion rule storage unit. In the figure, the forward conversion table 137Ta stores a conversion rule for an unprotected physical path name or a protected physical path name according to the format of the logical path name.

  In the present embodiment, the user or the application 11 can explicitly specify in the logical path name which of the two physical files of the unprotected state file and the protected state file is to be preferentially operated. it can. Specifically, when a physical file to be operated is designated preferentially, a predetermined identifier indicating the physical file to be operated is added to the file name included in the logical path name as the logical path name. . In the present embodiment, the identifier for the unprotected state file is a prefix “pla”. The identifier for the protection state file is a prefix “enc−”.

  In the figure, when a prefix “pla-” or a prefix “enc-” is added to a file name included in the logical path name, the prefix is converted to the unprotected physical path name. It is shown that this is done by removing more. Further, the conversion to the protected physical path name indicates that the prefix is removed from the file name, and the extension “.enc” indicating the protection state file is added to the file name.

  In addition, when a prefix is not added to the file name included in the logical path name, that is, when the physical file to be operated is not specified, the conversion to the unprotected physical path name is the same as the logical path name. It has been shown to be used. Further, the conversion to the protected physical path name indicates that the extension “.enc” indicating the protection state file is given to the logical path name.

  Thus, in the present embodiment, the “pla” prefix is an identifier indicating the unprotected state in the logical path name. The “enc-” prefix is an identifier indicating the protection state in the logical path name. On the other hand, the extension “.enc” is an identifier indicating a protection state in the physical path name.

  The reason why the logical path name is distinguished from the unprotected state and the protected state by using a prefix, not an extension, is that the logical path name is a path name used by the application 11. In other words, the application 11 may determine the file type based on the extension, and change the behavior based on the determination result. For example, if the file has an extension of “.txt”, the application 11 assumes that the file is in a text format and tries to interpret the data in the file. In view of such a point, it is considered that the extension of the application 11 unexpectedly to the logical path name used by the application 11 may cause the application 11 to malfunction. Therefore, in this embodiment, a prefix is assigned to the logical path name instead of an extension.

  Subsequently, the conversion unit 136 determines whether or not the physical file to be operated is explicitly specified (S153). That is, the conversion unit 136 determines whether the logical path name includes the prefix “pla” or the prefix “enc-”. When the operation target is explicitly specified (Yes in S153), the conversion unit 136 determines whether or not the protection state file is specified as the operation target (S154). That is, it is determined whether or not the prefix “enc−” is included in the logical path name. When the protection state file is designated as the operation target, that is, when the logical path name includes the prefix “enc-” (Yes in S154), the conversion unit 136 sets the protection state file as the priority file. The conversion result (unprotected physical path name and protected physical path name) is returned (S155). When the unprotected status file is designated as the operation target, that is, when the logical path name includes the prefix “pla” (No in S154), the conversion unit 136 selects the unprotected status file as the priority file. As a result, the conversion result (unprotected physical path name and protected physical path name) is returned (S156).

  On the other hand, when the physical file to be operated is not explicitly specified (No in S153), the conversion unit 136 makes an inquiry to the state management unit 134 to determine whether or not the application 11 is in the protection mode ( S157). When the application 11 is in the protection mode (Yes in S157), the conversion unit 136 checks whether or not there is a protection state file related to the protection physical path name obtained in Step S152 (S158). When the protection state file exists (Yes in S158), the conversion unit 136 sets the protection state file as a priority file and returns a conversion result (unprotected physical path name and protected physical path name) (S159).

  When the protection state file does not exist (No in S158), the conversion unit 136 checks whether or not the non-protection state file related to the non-protection physical path name obtained in Step S152 exists (S160). When the unprotected state file exists (Yes in S160), the conversion unit 136 returns the conversion result (unprotected physical path name and protected physical path name) using the unprotected state file as a priority file (S161). When the unprotected state file does not exist (No in S160), the conversion unit 136 returns an error indicating that the physical file corresponding to the logical path name does not exist (S162).

  When the application 11 is not in the protection mode (No in S157), the conversion unit 136 checks whether or not there is an unprotected state file related to the unprotected physical path name obtained in Step S152 (S163). If the unprotected state file exists (Yes in S163), the conversion unit 136 returns the conversion result (unprotected physical path name and protected physical path name) using the unprotected state file as a priority file (S164).

  When the unprotected state file does not exist (No in S163), the conversion unit 136 checks whether or not the protected state file related to the protected physical path name obtained in Step S152 exists (S165). When the protection state file exists (Yes in S165), the conversion unit 136 returns the conversion result (unprotected physical path name and protected physical path name) using the protection state file as a priority file (S166). When the protection state file does not exist (No in S165), the conversion unit 136 returns an error indicating that the physical file corresponding to the logical path name does not exist (S167).

  Thus, when the operation target is not explicitly specified, the priority operation target (here, the open target) is selected based on whether the application 11 is in the protection mode or the non-protection mode. The On the other hand, when the operation target is explicitly specified, the specified physical file is given priority as the operation target regardless of whether the application 11 is in the protection mode or the non-protection mode.

  Note that, as described with reference to FIG. F1, in the present embodiment, the physical file determined as the priority file by the conversion unit 136 is set as the open target. Therefore, when the operation target is explicitly specified in the logical file name to be opened, the specified physical file is opened regardless of whether the application 11 is in the protected mode or the non-protected mode. It is said. Therefore, for example, in the application 11 in the protection mode, the user can make an unprotected state file a browsing target. In addition, the user can set the protection state file as a browsing target in the application 11 in the non-protection mode. In this case, the user may specify the logical path name with the prefix “pla-” added to the file name as an editing target for the application 11.

  Next, a processing procedure when writing to a file will be described. FIG. 7 is a flowchart for explaining an example of a processing procedure of a file writing process. This figure shows the processing procedure executed when there is a write request from the application 11 for the currently opened file.

  In step S <b> 201, the write processing unit 132 of the file management unit 13 receives a file write request from the application 11. In the file write request, the file identifier of the write destination file, the write contents, and the like are specified.

  Subsequently, the write processing unit 132 makes an inquiry to the state management unit 134 to determine whether or not the application 11 is in the unprotected mode (S202). The processing content of step S202 may be the same as that of step S102 of FIG.

  When the application 11 is in the unprotected mode (Yes in S202), the write processing unit 132 causes the file system 12 to write to the unprotected state file corresponding to the file identifier specified in the write request (S203).

  Subsequently, the write processing unit 132 confirms whether or not the protection state file corresponding to the file relating to the file identifier (that is, the unprotected state file at the write destination) is stored in the protection state file storage unit 15 ( S204). Specifically, the write processing unit 132 acquires the protection physical path name of the protection state file from the file information storage unit 135 using the file identifier as a key, and the presence or absence of the protection state file corresponding to the protection physical path name. Confirm.

  If the corresponding protection state file exists (Yes in S204), the write processing unit 132 deletes the protection state file (S205). The protection state file is deleted because the content of the protection state file is older than the non-protection state file corresponding to the same logical file. Therefore, by deleting the protection state file, an attempt is made to prevent the protection state file having the old contents from being set as an operation target (opened). That is, later, when it is requested to open the protection state file corresponding to the logical file, steps S115 and S116 in FIG. 3 are executed. That is, a protected state file is generated based on a copy of the unprotected state file. As a result, the protected state file is opened in a state where the contents written to the unprotected state file are reflected.

  On the other hand, when the application 11 is in the protection mode (No in S202), the write processing unit 132 acquires the state of the physical file related to the specified file identifier from the file information storage unit 135 (S206). That is, information for identifying whether a physical file to be written is a protected state file or an unprotected state file is acquired.

  When the physical file to be written is an unprotected state file (Yes in S207), the write processing unit 132 acquires the unprotected physical path name and the protected physical path name related to the specified file identifier from the file information storage unit 135. (S208).

  For example, in the application 11, when an unprotected state file is opened during the unprotected mode, and then a protected state file of another file is opened, the application 11 enters the protected mode. In this state, a case where a write request is generated for the unprotected state file is a case where Yes is obtained in step S207.

  Subsequently, the write processing unit 132 deletes the record corresponding to the file identifier from the file information storage unit 135 (S209). Subsequently, the write processing unit 132 causes the file system 12 to close the physical file (unprotected state file) associated with the file identifier (S210). Subsequently, the write processing unit 132 generates a copy (copy) of the unprotected state file in the protected state file storage unit 15 and sets the copy to a protected state (S211). The copy destination physical path name is the protected physical path name obtained in step S208.

  Subsequently, the write processing unit 132 causes the file system 12 to open the copy destination protection state file (S212). Subsequently, the write processing unit 132 associates the file identifier obtained by opening, the value indicating the protection state, and the non-protected physical path name and the protected physical path name obtained in Step S208 with each other, and creates a file information storage unit. 135 is recorded (S213).

  Subsequently, the write processing unit 132 protects (encrypts) the written content, and causes the file system 12 to write to the opened protected state file (S214). By writing to the protection state file based on the copy of the non-protection state file, it is possible to avoid writing the contents of the protection state (encrypted contents) in the non-protection state file. That is, it is possible to prevent the unprotected state file from being put into the protected state against the intention of the user or the application 11. Step S211 is one of the timings of occurrence of a state in which both an unprotected state file and a protected state file exist for one file, along with step S115 in FIG. Note that the copy may be put into a protected state after the unprotected state file is written to the copy.

  On the other hand, when the file to be written is a protection state file (No in S207), the write processing unit 132 sets the write content to the protection state and causes the file system 12 to execute writing to the protection state file (S215). .

  As described above, the write processing unit 132 performs a write to the requested file with respect to a write request to the file conforming to the mode (non-protected mode or protected mode). On the other hand, in the protected mode, when writing to the unprotected state file is requested, the write processing unit 132 writes to the protected state file based on the copy of the unprotected state file.

  Therefore, in this case, writing to the opened unprotected state file is not performed. That is, when the unprotected state file is opened next time, the written content is not included. The occurrence of such a situation is considered to be disadvantageous for the user. However, in this embodiment, in order to prioritize the disadvantages caused by the unprotected state file being set to the protected state and suppress the occurrence of the disadvantages, the generation of the replica and the writing to the replica are performed. ing.

  That is, for example, when the unprotected state file is a setting file, there is a possibility that the application 11 may not be activated when the setting file is protected.

  On the other hand, as described in FIG. 3, the transition to the protection mode is performed when the user's permission is obtained. Then, it can be considered that the user knows that writing to the unprotected state file cannot be performed. Thus, the disadvantage of not being written to the unprotected state file is considered to be scheduled for the user. Rather, the fact that the writing to the unprotected state file has been performed in the protected mode can be interpreted that the user wants to put the written content in the protected state. In other words, it can be considered that it is contrary to the user's intention to save the written content in the protected mode in an unprotected state.

  Based on the above idea, in this embodiment, writing to the unprotected state file in the protected mode is suppressed.

  Note that when writing to the protected state file is performed, the unprotected state file is not deleted. This is because in this embodiment, if an unprotected state file is deleted, it is difficult to restore the unprotected state file. That is, when there is no unprotected state file at the time of opening, the unprotected state file is not generated based on the copy of the protected state file. The reason why the unprotected state file is not generated based on the copy of the protected state file is that the contents of the protected state file are put into the unprotected state. That is, the existence significance of the protection state file is lost.

  Note that the processing procedure at the time of generating a file may replace the writing process in FIG. 7 with an open process.

  Next, a processing procedure when acquiring a list of logical path names will be described. Acquisition of a list of logical path names is executed, for example, when the application 11 displays a dialog (such as a file dialog) for selecting a file to be operated.

  FIG. 8 is a flowchart for explaining an example of a processing procedure when acquiring a list of logical path names.

  In step S <b> 401, the list response unit 133 of the file management unit 13 receives a logical path name list acquisition request from the application 11. Note that the name of the specific directory (directory name) is specified in the acquisition request. Subsequently, the list response unit 133 acquires a list of physical path names of physical files belonging to the directory related to the directory name from the file system 12 (S402).

  Subsequently, the list response unit 133 requests the conversion unit 136 to convert each acquired physical path name into a logical path name. In response to the request, the conversion unit 136 converts each physical path name into a logical path name based on the reverse conversion table 137Tb stored in the conversion rule storage unit 137 (S403).

  FIG. 9 is a diagram illustrating a configuration example of an inverse conversion table stored in the conversion rule storage unit. In the figure, the reverse conversion table 137TbT2 stores a conversion rule from a physical path name to a logical path name for each protection mode and non-protection mode.

  Specifically, in the protection mode, if the extension “.enc” is not added to the physical path name, the prefix “pla” is added. That is, in the case of a path name of an unprotected state file, a prefix “pla” that clearly indicates the unprotected state is added to the logical path name. Further, if the extension “.enc” is given to the physical path name, the prefix “enc-” is given. That is, if it is a path name of a protection state file, a prefix “enc-” that clearly indicates the protection state is added to the logical path name.

  On the other hand, in the non-protection mode, if the extension “.enc” is not given to the physical path name, the logical path name is left as the physical path name. This is because, in the non-protected mode, it is considered that it is not necessary to clearly indicate the non-protected state in the logical path name of the non-protected file. Further, if the extension “.enc” is given to the physical path name, the prefix “enc-” is given. That is, if it is a path name of the protection state file, an “enc-” prefix that clearly indicates the protection state is added to the logical path name.

  Note that the conversion rules in the protection mode of FIG. 9 may always be adopted without distinction of operation modes.

  Subsequently, the list response unit 133 returns (responds) a list of logical path names as conversion results to the application 11 (S404). As a result, the application 11 can display each physical file by a logical path name in a file dialog or the like, for example. As a result, the physical path name can be hidden from the user.

  Further, a logical path name can be selected as an operation target, and, for example, consistency with the file open processing described in FIG. 3 can be achieved. This is because the open processing unit 131 uses the logical path name as input information in the file open processing.

  As described above, according to the present embodiment, an unprotected state file and a protected state file can be managed for one file. Then, the operation target is appropriately selected depending on whether the mode is the non-protection mode or the protection mode. Therefore, it is possible to appropriately avoid the unprotected file from being changed to the protected state against the intention of the user or the application 11. As a result, convenience related to file protection can be improved.

  However, when the operation target is explicitly specified in the logical file name from the user or the application 11 or the like, the specified physical file is set as the operation target. Therefore, the convenience relating to file protection can be further improved compared to the case where the operation target is completely automatically selected in accordance with the protection mode or the non-protection mode.

  Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Therefore, the points not particularly mentioned may be the same as those in the first embodiment.

  FIG. 10 is a diagram illustrating a software configuration example of the file management apparatus according to the second embodiment. In FIG. 10, the same parts as those in FIG.

  In FIG. 10, the file management unit 13 a is not included in the file system 12. The file management unit 13a exists for each application 11. That is, the file management unit 13 in the first embodiment is an example implemented so as to expand the function of the file system 12, whereas the file management unit 13 a in the second embodiment uses the application 11. An example implemented to extend functionality is shown. FIG. 10 shows a state of loading onto the memory. In the second embodiment, only one file storing a program that functions as the file management unit 13a is sufficient. FIG. 10 shows that the program is loaded for each activation unit of the application 11. The file management unit 13a also includes an open processing unit 131, a write processing unit 132, a list response unit 133, a status management unit 134, a file information storage unit 135, a conversion unit 136, a conversion rule storage unit 137, and the like. Is not shown.

  The processing procedure executed by the file management unit 13a may be the same as that of the file management unit 13 in the first embodiment. However, for this purpose, the file management unit 13 a needs to hook (capture) a file operation request to the file system 12 by the application 11. In order to hook the operation request, for example, a mechanism called an API hook may be used.

  As the name implies, the API hook is a mechanism for hooking an API call (here, a request to the file system 12) by the application 11.

  Specifically, the file management unit 13a is implemented as a DLL (Dynamic Link Library). The DLL is registered in the OS. When the application 11 is activated, the OS requests the application 11 to load the registered DLL by a window message. The application 11 loads the DLL in response to the request. Therefore, the DLL is loaded into the virtual address space of the application 11. When the DLL is loaded, an area (referred to as an import area or an import section) containing a list of API addresses used by the application 11 included in the virtual space address is stored in the DLL. Rewrite as convenient. For example, an API for opening a file or an API for writing is used as an API for opening a file (that is, an open processing unit 131) or an API for writing (that is, a writing processing unit 132). ) Address. As a result, even if the application 11 intends to call an API for opening a file or an API for writing, the call is made to the file management unit 13a. As a result, the file management unit 13a can perform the same processing as in the first embodiment without correcting the source code of the application 11.

  However, a publicly known technique that is a mechanism or mechanism other than the API hook and can obtain the same effect may be used.

  The file management unit 13a is loaded for each activation unit of the application 11. Therefore, the state management unit 134 in the file management unit 13a may manage the state of its own startup unit.

  In each of the above embodiments, the conversion unit 136 is an example of a determination unit, a first selection unit, and a second selection unit. The open processing unit 131 is an example of a reception unit and an open unit.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
A procedure for accepting a request to open the first file with respect to the start unit of the file operation program capable of operating multiple files,
A procedure for determining whether a predetermined identifier is included in the path name specified in the received request to open the first file;
When the path identifier includes the predetermined identifier, a procedure for selecting a protected state file or an unprotected state file of the first file as an open target according to the predetermined identifier;
When the path name does not include the predetermined identifier and a protected state file is not opened with respect to the activation unit, the unprotected state file of the first file is selected as an open target, and the activation is performed. When a protection status file is opened for a unit, a procedure for selecting the protection status file of the first file as an open target; and
A file management method in which a computer executes a procedure for opening a protected state file or an unprotected state file of the first file selected as the opening target.
(Appendix 2)
The opening procedure is when the unprotected state file of the first file is selected as an open target, and when the protected state file is opened with respect to the activation unit, the copy of the unprotected state file is performed. The file management method according to appendix 1, wherein a protection state file is generated based on the above and the protection state file is opened.
(Appendix 3)
When the acquisition of the path name of the protected state file and the unprotected state file stored in the storage unit is requested for the activation unit, the path name of the protected state file or the unprotected state file is The file management method according to appendix 1 or 2, wherein the computer executes a procedure of responding to the result of assigning the predetermined identifier corresponding to the protected state file or the unprotected state file.
(Appendix 4)
A reception unit that accepts a request to open a first file with respect to a unit for starting a file operation program capable of operating multiple files;
A determination unit that determines whether a predetermined identifier is included in the path name specified in the received request to open the first file;
A first selection unit that selects a protected state file or an unprotected state file of the first file as an open target according to the predetermined identifier when the path identifier includes the predetermined identifier; ,
When the path name does not include the predetermined identifier and a protected state file is not opened with respect to the activation unit, the unprotected state file of the first file is selected as an open target, and the activation is performed. When a protection state file is opened with respect to the unit, a second selection unit that selects the protection state file of the first file as an opening target; and
A file management apparatus comprising: an open unit that opens a protected state file or an unprotected state file of the first file selected as the opening target.
(Appendix 5)
In the case where the unprotected state file of the first file is selected as an open target, and the open unit is a copy of the unprotected state file when the protected state file is opened with respect to the activation unit, The file management device according to appendix 4, wherein a protection state file is generated based on the protection state file and the protection state file is opened.
(Appendix 6)
When the acquisition of the path name of the protected state file and the unprotected state file stored in the storage unit is requested for the activation unit, the path name of the protected state file or the unprotected state file is The file management apparatus according to appendix 4 or 5, further comprising a response unit that responds to a result of assigning the predetermined identifier corresponding to the protected state file or the unprotected state file.
(Appendix 7)
A procedure for accepting a request to open the first file with respect to the start unit of the file operation program capable of operating multiple files,
A procedure for determining whether a predetermined identifier is included in the path name specified in the received request to open the first file;
When the path identifier includes the predetermined identifier, a procedure for selecting a protected state file or an unprotected state file of the first file as an open target according to the predetermined identifier;
When the path name does not include the predetermined identifier and a protected state file is not opened with respect to the activation unit, the unprotected state file of the first file is selected as an open target, and the activation is performed. When a protection status file is opened for a unit, a procedure for selecting the protection status file of the first file as an open target; and
A file management program for causing a computer to execute a procedure for opening a protected state file or an unprotected state file of the first file selected as the opening target.
(Appendix 8)
The opening procedure is when the unprotected state file of the first file is selected as an open target, and when the protected state file is opened with respect to the activation unit, the copy of the unprotected state file is performed. 8. The file management program according to appendix 7, wherein a protection state file is generated based on the above and the protection state file is opened.
(Appendix 9)
When the acquisition of the path name of the protected state file and the unprotected state file stored in the storage unit is requested for the activation unit, the path name of the protected state file or the unprotected state file is The file management program according to appendix 7 or 8, which causes the computer to execute a procedure for responding to the result of assigning the predetermined identifier corresponding to the protected state file or the unprotected state file.

DESCRIPTION OF SYMBOLS 11 Application 12 File system 13, 13a File management part 14 Unprotected state file storage part 15 Protected state file storage part 100 Drive apparatus 101 Recording medium 102 Auxiliary storage apparatus 103 Memory apparatus 104 CPU
105 interface device 106 display device 107 input device 131 open processing unit 132 write processing unit 133 list response unit 134 state management unit 135 file information storage unit 136 conversion unit 137 conversion rule storage unit B bus

Claims (5)

A procedure for accepting a request to open the first file with respect to the start unit of the file operation program capable of operating multiple files,
A procedure for determining whether a predetermined identifier is included in the path name specified in the received request to open the first file;
When the path identifier includes the predetermined identifier, a procedure for selecting a protected state file or an unprotected state file of the first file as an open target according to the predetermined identifier;
When the path name does not include the predetermined identifier and a protected state file is not opened with respect to the activation unit, the unprotected state file of the first file is selected as an open target, and the activation is performed. When a protection status file is opened for a unit, a procedure for selecting the protection status file of the first file as an open target; and
A file management method in which a computer executes a procedure for opening a protected state file or an unprotected state file of the first file selected as the opening target.   The opening procedure is when the unprotected state file of the first file is selected as an open target, and when the protected state file is opened with respect to the activation unit, the copy of the unprotected state file is performed. The file management method according to claim 1, wherein a protection state file is generated based on the file and the protection state file is opened.   When the acquisition of the path name of the protected state file and the unprotected state file stored in the storage unit is requested for the activation unit, the path name of the protected state file or the unprotected state file is The file management method according to claim 1 or 2, wherein the computer executes a procedure of responding to a result of assigning the predetermined identifier corresponding to a protected state file or the unprotected state file. A reception unit that accepts a request to open a first file with respect to a unit for starting a file operation program capable of operating multiple files;
A determination unit that determines whether a predetermined identifier is included in the path name specified in the received request to open the first file;
A first selection unit that selects a protected state file or an unprotected state file of the first file as an open target according to the predetermined identifier when the path identifier includes the predetermined identifier; ,
When the path name does not include the predetermined identifier and a protected state file is not opened with respect to the activation unit, the unprotected state file of the first file is selected as an open target, and the activation is performed. When a protection state file is opened with respect to the unit, a second selection unit that selects the protection state file of the first file as an opening target; and
A file management apparatus comprising: an open unit that opens a protected state file or an unprotected state file of the first file selected as the opening target. A procedure for accepting a request to open the first file with respect to the start unit of the file operation program capable of operating multiple files,
A procedure for determining whether a predetermined identifier is included in the path name specified in the received request to open the first file;
When the path identifier includes the predetermined identifier, a procedure for selecting a protected state file or an unprotected state file of the first file as an open target according to the predetermined identifier;
When the path name does not include the predetermined identifier and a protected state file is not opened with respect to the activation unit, the unprotected state file of the first file is selected as an open target, and the activation is performed. When a protection status file is opened for a unit, a procedure for selecting the protection status file of the first file as an open target; and
A file management program for causing a computer to execute a procedure for opening a protected state file or an unprotected state file of the first file selected as the opening target.

Images