# US 2025/0094583 A1 · Apparatus and method for protecting data in linux-based operating system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094583 A1
- Document ID: US20250094583A1
- Status: Published application
- Kind: A1
- Application number: 18/572,230
- Filed: 2023-10-27
- Published: 2025-03-20
- Earliest claimed: 2022-11-17
- Assignees: REALSECU Co., Ltd.
- Inventors: Myeong Won SEO
- Web page: https://patentgrep.com/patent/US20250094583A1

## CPC

- G06F 21/565: {by checking file integrity}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/60: Protecting data
- G06F 21/6209: {to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- H04L 9/08: Key distribution {or management, e.g. generation, sharing or updating, of cryptographic keys or passwords (network architectures or network communication protocols for supporting key management in a packet data network H04L63/06)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Provided is an apparatus for protecting data in a Linux-based operating system, the apparatus including: a physical storage device; and a processor provided with a user application, a user library, a virtual file system (VFS), a kernel-based file system, a Filesystem in Userspace (FUSE) kernel driver, and a FUSE user daemon as software modules. A file containing protection target data may be safely protected by being stored in a FUSE storage area that is accessible only in a FUSE mount state.

## Claims

### Claim 1

An apparatus for protecting data, comprising:
a physical storage device; and
a processor provided with a user application, a user library, a virtual file system (VFS), a kernel-based file system, a Filesystem in Userspace (FUSE) kernel driver, and a FUSE user daemon as software modules,
wherein, when the user application provides request information requesting access to a FUSE file path to the user library, the user library provides the request information to the VFS,
when a handler for the FUSE file path included in the request information is registered in advance, the VFS determines that a state is a FUSE mounted state and provides the request information to the FUSE kernel driver that is registered in advance,
the FUSE kernel driver provides the request information to the FUSE user daemon,
the FUSE user daemon directly accesses a file at a file address of the physical storage device predetermined to correspond to the FUSE file path through the kernel-based file system,
the FUSE user daemon returns access result information for the file of the file address of the physical storage device to the FUSE kernel driver,
the FUSE kernel driver returns the access result information for the file to the VFS,
the VFS returns the access result information for the file to the user library,
the user library returns the access result information for the file to the user application, and
the file for the FUSE file path includes protection target data.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the request information further includes user and group identification information, and
the FUSE kernel driver is configured to:
check whether the user and group identification information included in the request information corresponds to user and group identification information predetermined to match the FUSE file path;
when the user and group identification information included in the request information corresponds to the user and group identification information predetermined to match the FUSE file path, determine that authentication is successful; and
only when the authentication is successful, provide the request information to the FUSE user daemon.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the processor is further provided with a FUSE daemon program and a FUSE library program, and
when the handler for the FUSE file path included in the request information is not registered in the VFS, the user library determines that a state is a FUSE unmounted state and executes the FUSE daemon program,
the FUSE daemon program requests the file address of the physical storage device corresponding to the FUSE file path from the kernel-based file system according to an execution event, and
when the kernel-based file system returns the file address of the physical storage device, the FUSE daemon program stores the file address of the physical storage device to match the FUSE file path, registers self as the FUSE user daemon, provides the FUSE file path and user and group identification information corresponding to the FUSE file path to the FUSE kernel driver to be registered through the FUSE library program, and then determines that a state is the FUSE mounted state.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein a physical file address of the file containing the protection target data in the FUSE mounted state is identical to a physical file address of the file containing the protection target data in the FUSE unmounted state.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein, when an access request for data of the file recorded at the file address of the physical storage device is a read request, the FUSE user daemon reads an original file, decrypts a result of the reading, and returns a result of the decryption, and when the access request is a write request, the FUSE user daemon encrypts content to be written and writes the content to an original file.

### Claim 6

A method of protecting data performed by an apparatus including a physical storage device and a processor provided with a user application, a user library, a virtual file system (VFS), a kernel-based file system, a Filesystem in Userspace (FUSE) kernel driver, and a FUSE user daemon as software modules, the method comprising:
providing, by the user application, request information requesting access to a FUSE file path to the user library;
providing, by the user library, the request information to the VFS;
when a handler for the FUSE file path included in the request information is registered in advance, determining, by the VFS, that a state is a FUSE mounted state and providing the request information to the FUSE kernel driver that is registered in advance;
providing, by the FUSE kernel driver, the request information to the FUSE user daemon;
directly accessing, by the FUSE user daemon, a file at a file address of the physical storage device predetermined to correspond to the FUSE file path through the kernel-based file system;
returning, by the FUSE user daemon, access result information for the file of the file address of the physical storage device to the FUSE kernel driver;
returning, by the FUSE kernel driver, the access result information for the file to the VFS;
returning, by the VFS, the access result information for the file to the user library; and
returning, by the user library, the access result information for the file to the user application,
wherein the file for the FUSE file path includes protection target data.

### Claim 7 (depends on 6)

The method of claim 6, wherein the request information further includes user and group identification information, and
the FUSE kernel driver is configured to:
check whether the user and group identification information included in the request information corresponds to user and group identification information predetermined to match the FUSE file path;
when the user and group identification information included in the request information corresponds to the user and group identification information predetermined to match the FUSE file path, determine that authentication is successful; and
only when the authentication is successful, provide the request information to the FUSE user daemon.

### Claim 8 (depends on 7)

The method of claim 7, wherein the processor is further provided with a FUSE daemon program and a FUSE library program, and
the method further comprising:
determining, by the user library, that a state is a FUSE unmounted state and executing the FUSE daemon program when the handler for the FUSE file path included in the request information is not registered in the VFS;
requesting, by the FUSE daemon program, the file address of the physical storage device corresponding to the FUSE file path from the kernel-based file system according to an execution event; and
when the kernel-based file system returns the file address of the physical storage device, storing, by the FUSE daemon program, the file address of the physical storage device to match the FUSE file path, registering, by the FUSE daemon program, self as the FUSE user daemon, providing the FUSE file path and user and group identification information corresponding to the FUSE file path to the FUSE kernel driver to be registered through the FUSE library program, and then determining that a state is a FUSE mounted state.

### Claim 9 (depends on 8)

The method of claim 8, wherein a physical file address of the file containing the protection target data in the FUSE mounted state is identical to a physical file address of the file containing the protection target data in the FUSE unmounted state.

### Claim 10 (depends on 6)

The method of claim 6, wherein, when an access request for data of the file recorded at the file address of the physical storage device is a read request, the FUSE user daemon reads an original file, decrypts a result of the reading, and returns a result of the decryption, and when the access request is a write request, the FUSE user daemon encrypts content to be written and writes the content to an original file.

### Claim 11

A method of safely protecting an encryption key used to protect data communication in a network, the method comprising:
implementing a Filesystem in Userspace (FUSE) mount to access a FUSE partition in which key data for the encryption key is stored;
after the FUSE mount, writing or reading, by a FUSE user daemon, the key data in the FUSE partition; and
performing FUSE unmount,
wherein a virtual file system (VFS) processes mount of a file system.

### Claim 12 (depends on 11)

The method of claim 11, wherein the VFS converts a path of the key data loaded on the FUSE partition and a path of process-related data to be identical.

### Claim 13 (depends on 11)

The method of claim 11, wherein the FUSE mount is implemented when at least one of a user ID and a group ID is the same.
