Table of Contents
Before proceeding, you need to register the applications you want to allow and the path information to which these applications will have access within the FilingBox MEGA2 v2 Server.
Important
If an application that is not registered as an allowed app accesses a file stored in the FilingBox MEGA2 v2 Server, a 'read-only fake file' will be provided. (Since a fake file is provided, the application will not be able to access the file properly.)
Register allowed apps
To register an allowed app on the client, follow the steps below.
-
Navigate to the location where the ‘./fbmegas’ executable file is stored. (e.g., /namusoft/megaclient)
Execute the following command.cd /namusoft/megaclient - Execute the following command.
./fbmega –alwapp –add –p app_path –d access_path –o permissions- ‘-p app_path’
- The path and filename of the executable file of the app you want to allow access (e.g., /usr/bin/vi)
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 128 characters
- Default Value: None
If no value is entered or if a value exceeding 128 characters is entered, the following error message will appear.
Screen when no value is entered
Screen when a value exceeding 128 characters is entered
If a non-existent app path value is entered, the following error message will appear.
Important
Be sure to enter the 'absolute path' value.
- ‘-d access_path’
- The path the app will access on this device (e.g., / )
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 128 characters
- Default Value: None
If no value is entered or if a value exceeding 128 characters is entered, the following error message will appear.
Screen when no value is entered
Screen when a value exceeding 128 characters is entered
If a non-existent path value is entered, the following error message will appear.
Important
When specifying the path, it must be defined relative to the folder mounted on the FilingBox MEGA2 v2 Server. For example, if '/root/mount_app' is mounted at login, and the same path is used when registering the allowed app, you should enter '/'.
- ‘-o permissions’
- Access permissions for the specified path (Read/Write: ‘rw’, Read-only: ‘ro’, Append-only: ‘ao’, Versioning File Creation: ‘rwv’)
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 3 characters
- Default Value: None
If no value is entered or if a value exceeding 3 characters is entered, the following error message will appear.
Screen when no value is entered
Screen when the value exceeds 3 characters or when a value other than [ro, rw, ao, rwv] is entered
Note
Read/Write: This app can access files under the specified folder with 'Read/Write' permissions.
Note
Read-only: This app can access files under the specified folder with 'Read' permissions only. (It cannot perform any write actions.)
Note
Appendable: This app can add files to the specified folder. However, it cannot perform 'Read/Write/Delete' operations on existing files stored on the server.
Note
Appendable: This app has 'Read/Write' permissions, but if it modifies (including delete) any existing files on the server, backup files will be created. These backup files can be used to restore the original files.
-
After executing command 2, you will need to enter your login password for authentication.
Important
For security reasons, the entered values will not be displayed on the screen.
- password
- Login password
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 20 characters
- Default Value: None
- After successfully executing command 3, you will need to enter the OTP value for secondary authentication.
Important
For security reasons, the entered values will not be displayed on the screen.
The input rules are as follows:
- Input Rules: Numbers
- Input Length: 6 characters
- Default Value: None
- If secondary authentication is completed successfully, the message “add app success” will be displayed.
Note
If the command is executed before login and mount actions, the error message ‘not mounted!’ will appear.
Note
If you try to register an already registered app, the following error message will appear.
View allowed app list
To view the list of allowed apps registered on the FilingBox MEGA2 v2 Server from the client, follow the steps below.
-
Navigate to the location where the ‘./fbmega’ executable file is stored. (e.g., /namusoft/megaclient)
Execute the following command:cd /namusoft/megaclient - Execute the following command:
./fbmega –alwapp –list - The result of executing the command is as follows:
- IP: Client IP address
- Mode: Permission information (‘rw’ : Read/Write, ‘r’ : Read-only)
- Application: Information of registered app (Name and full path of the app's executable file)
- Folder: Directory path that the app can access (Relative path will be shown based on the mounted directory.)
Important
If the mounted path is ‘/root/mount_point’ and the accessible directory for the app is specified as ‘/root/mount_point/test_1023,’ the 'Folder' column will show ‘/test_1023’ when the command is executed. If the accessible directory is specified as ‘/root/mount_point,’ no value will be shown in the 'Folder' column.
Note
If you execute the command before performing the login and mount actions, the error message 'not mounted!' will appear.
Delete allowed app
To delete an allowed app registered on the FilingBox MEGA2 v2 Server from the client, follow the steps below.
- Navigate to the location where the ‘./fbmegas’ executable file is stored. (e.g., /namusoft/megaclient)
cd /namusoft/megaclient - Execute the following command:
./fbmega –alwapp –rm –p app_path –d access_path- ‘-p app_path’
- The path where the app's executable file is stored, including the executable file name (e.g., /usr/bin/vi)
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 128 characters
- Default Value: None
If you fail to enter the app path or exceed the 128-character limit, the following error messages will appear:
Screen when app path is not entered
Screen when app path exceeds 128 characters
Important
You must enter the same value you used when registering this app. If you enter a different value, the following error message will appear.
- '-d access_path'
- The path that the app will access on this device (e.g., / )
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 128 characters
- Default Value: None
If you fail to enter the access path or exceed the 128-character limit, the following error messages will appear:
Screen when the access path is not entered:
Screen when the access path exceeds 128 characters:
Important
You must enter the same values as those you used when registering the app. If you enter a different value, the following error message will appear.
- After executing the second command, you will be asked to enter the login password for authentication.
Important
For security reasons, the values you enter will not be displayed on the screen.
- password
- Login password
- Input Rules: No restrictions on letters, numbers, or special characters
- Input Length: 1 ~ 20 characters
- Default Value: None
- If the second command is executed successfully, you will be asked to input an OTP value for two-factor authentication.
Important
For security reasons, the values you enter will not be displayed on the screen.
The input rules are as follows:
- Input Rules: Numeric values only
- Input Length: 6 characters
- Default Value: None
- If you enter the login password correctly, the "rm app success" message will be displayed.
Note
If you run the command before performing login and mount actions, the error message 'not mounted!' will appear.