AZSTOKE_RIGDOCKS Bridge_ver2.1.0

■ Configuration changes

1. Adding a Resident App: The RIGDOCKS application itself is added as a resident app (in the notification area on Windows, and the menu bar on macOS). Plugins (rank modules) are loaded by the resident app, not REAPER. APIs and server functions that do not use REAPER will work even if REAPER is not running.

2. Separation of REAPER extension: The REAPER side will consist only of the REAPER extension (`reaper_RIGDOCKS`), and the configuration will be changed so that REAPER operations are requested from a resident application.

3. Added rigcmd: Added [rigcmd], a command-line tool that allows you to execute the RIGDOCKS API from the shell with a single command.

4. Management Channel: Added a dedicated management channel within the PC for RIGDOCKS Bridge, REAPER extension, and rigcmd to control resident applications.

5. Logs: Change the log format to separate files by product and place them under date folders (keeping the most recent 10 days' worth).

■Screen changes

The main screen has been reconfigured to allow switching between tabs on the left (Plugins / License / Server / Client / Settings).

■ Plugin tab

1. Package Installation: Added a method where RIGDOCKS Bridge installs packages without displaying an installer screen.

2. Signature Verification: Verifies the code signatures of packages and modules. Packages that fail verification will not be installed or loaded.

3. Update display: Displays a list of installed plugins that have updates available.

4. Plugin Settings Screen: Settings for each plugin can now be changed in the settings area on the right side of the list. Since each plugin declares its own settings, the settings can be configured on the same screen even as the number of plugins increases.

5. Additional Data Installation: The plugin now allows you to select and install only the necessary additional data (such as the SILVER Whisper model) from the settings screen.

6. Offline List: Saves the last catalog you retrieved, allowing you to view the list even when offline.

■License tab
You can perform the same operations on RIGDOCKS Bridge as you would on a website's license management page.

1. Checking License Status: Displays the license status, start date, and expiration date for each product.

2. Obtain a trial version. Obtain a trial version license.

3. License Sharing: Adding and removing license sharing to other users

■Server tab: Settings for the server receiving external connections.

1. Listening: Start/stop the server, change the listening address and port. Fingerprint: Display the server fingerprint and regenerate the server key.

2. The QR code displays the URL that the client uses to register the connection destination.

3. Application Acceptance: Accepts connection requests from clients for a limited time, and approves/rejects them from a list of pending approvals.

4. Approved Clients: View list, rename, delete, manually add client keys.

5. Connected Clients: A list of currently connected clients.
   Log writing: Turn communication log recording ON/OFF for each client (default is OFF).
   

■Client tab (new)
This setting is for the user initiating a connection. It allows you to register connection destinations via a connection URL and manage registered destinations.

■ Settings tab

1. RIGDOCKS Bridge Update: Now displays if there are any updates available and allows you to update RIGDOCKS Bridge itself from the screen.

2. Download: Displays a list of shared data (such as error messages) retrieved from the server, allowing for re-retrieval.

3. Notification: Added an option to turn on/off OS banner notifications displayed by the RIGDOCKS device.

4. Accounts: View logged-in accounts and computers in use, add logout option.

5. End User License: View the status of your agreement to the Terms of Use and the full text (PDF).

6. Third-Party Disclosure: Displays the licenses for third-party software included in RIGDOCKS Bridge.

7. File Access Settings: The API's path restrictions for handling files (folders with access denied/allowed) can now be edited from the screen.
   

■ Changes to License and Terms of Use

1. Agreement to Terms of Use: The plugin will no longer be usable until you agree to the terms of use. If the terms are revised, you will not be able to use the plugin until you agree again.

2. Automatic License Renewal for RIGDOCKS: The system automatically renews the session, retrieves the terms of service, and verifies the license upon startup and every 24 hours. No login is required.

3. Offline operation: When offline, the system checks using the saved license file. If logged in, you can open RIGDOCKS Bridge and perform operations that do not require an internet connection, even when offline.

4. Computers in Use: Only one computer can be used at a time. You can check and switch between computers in use from RIGDOCKS Bridge. License Deactivation: When the license is deactivated, delete the license file saved on your PC.

5. Automatic login: Change your password to prevent repeated automatic logins with incorrect passwords.

■ Changes to communications and security

1. Unified listening: The RIGDOCKS unit receives external connections on a single port and distributes them to the destination plugin. No separate port is required for each plugin.

2. Default settings: For new installations, the listening address is `127.0.0.1` (PC only), port is `23760`, and server execution is OFF. Environments with saved settings will retain the previous values. TLS: Only TLS 1.3 is accepted (only AEAD cipher suite, only ephemeral key exchange).

3. Authentication Information: Server keys and authorized client information are stored together in a common RIGDOCKS location. This information will not be deleted even after uninstallation.

4. Connection restrictions: Added limits on the number of simultaneous connections, the number of simultaneous connections before authentication, the message size before authentication, and the time limit until authentication.

5. OS Notifications: The OS displays banner notifications when a client connects, when a connection request is received, when an unauthorized key is rejected, or when suspicious communication is detected.

6. Module Availability: A mechanism has been added to determine whether each plugin can be used via external connections.

7. Rejecting older generation programs: Modified to prevent loading of unsupported older generation modules.

8. Path Restrictions: Protected folders, such as those in RIGDOCKS/RIGDOCKS Bridge, can no longer be accessed from APIs that handle files.