
RIGDOCKS Bridgever 2.1.0
AZSTOKE_RIGDOCKS Bridge_ver2.1.0
- Now independent of REAPER and runs as a resident app
- Added a management screen
- Plugin installation, settings, licences and connections can now all be managed from RIGDOCKS Bridge
- Added rigcmd, a program that runs RIGDOCKS APIs from the command line
Release
Detail
Architecture changes
- Resident app : Added the RIGDOCKS core 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 instead of REAPER. APIs and server features that do not use REAPER work even when REAPER is not running
- Separate REAPER extension : The REAPER side is now only a REAPER extension (
reaper_RIGDOCKS), and the resident app asks it to perform REAPER operations - rigcmd : Added [rigcmd], a command-line tool that runs a RIGDOCKS API from the shell in a single command
- Management channel : Added a [management channel], local to the PC, through which RIGDOCKS Bridge, the REAPER extension and rigcmd control the resident app
- Logs : Logs are now split into a file per product and stored under dated folders (the 10 most recent days are kept)
Screen changes
The main screen now switches between tabs on the left (Plugins / License / Server / Client / Settings).
Plugins tab
- Package installation : Added installation in which RIGDOCKS Bridge fetches and installs the package without showing an installer
- Signature verification : Code signatures of packages and modules are verified. Anything that fails verification is neither installed nor loaded
- Update status : The list shows whether updates are available for installed plugins
- Plugin settings screen : Each plugin's settings can be changed in the settings area to the right of the list. Each plugin declares what the screen shows, so new plugins can be configured on the same screen
- Additional data installation : Additional data used by plugins (such as SILVER's Whisper models) can be installed from the settings screen, choosing only what you need
- Offline list : The last catalogue retrieved is saved, so the list is shown even when offline
License tab
The same operations as the licence management page on the website can be done in RIGDOCKS Bridge.
- Licence status : Shows each product's licence status, start date and expiry date
- Trial : Get a trial licence
- Licence sharing : Add and remove sharing with other users
Server tab
Settings for the side that accepts connections from outside.
- Listening : Start / stop the server, and change the listening address and port
- Fingerprint : Show the server's fingerprint and regenerate the server key
- Connection QR : Shows, as a QR code, the URL that clients use to register this server
- Request acceptance : Accept connection requests from clients for a limited time, and approve / reject them from the pending list
- Approved clients : View the list, rename, delete, and add client keys manually
- Connected clients : A list of the clients currently connected.
- Log writing : Turn communication logging ON / OFF for each client (OFF by default)
Client tab (new)
Settings for connecting out to another machine. Register destinations from a connection URL and manage registered destinations.
Settings tab
- RIGDOCKS Bridge updates : Shows whether an update is available, and lets you update RIGDOCKS Bridge itself from the screen
- Downloads : Lists the shared data fetched from the server (such as error messages) and lets you fetch it again
- Notifications : Added ON / OFF for the OS banner notifications from the RIGDOCKS core
- Account : Shows the signed-in account and the computer in use, and adds sign-out
- End user licence : Shows whether the terms of use have been accepted, and their text (PDF)
- Third-party notices : Shows the licences of third-party software included in RIGDOCKS Bridge
- File access settings : The path restrictions for APIs that handle files (denied / allowed folders) can be edited on screen
Licence and terms-of-use changes
- Accepting the terms of use : Plugins cannot be used until the terms of use are accepted. If the terms are revised, plugins cannot be used until they are accepted again
- Automatic licence renewal : When the RIGDOCKS core starts and every 24 hours, it automatically renews the session, fetches the terms of use and checks the licence. There is no need to sign in again
- Offline behaviour : When offline, the saved licence file is used for checks. If you are signed in, you can open RIGDOCKS Bridge offline and do anything that does not need a connection
- Computer in use : Only one computer can be used at a time. You can check and switch the computer in use from RIGDOCKS Bridge
- Licence removal : When a licence is removed, the licence file saved on the PC is deleted
- Automatic sign-in : Automatic sign-in is no longer retried repeatedly when the password is wrong
Communication and security changes
- Single listener : The RIGDOCKS core accepts external connections on a single port and routes them to the destination plugin. Plugins no longer open their own ports
- Default settings : New installations use the listening address
127.0.0.1(this PC only), port23760, and the server OFF. Environments with saved settings keep their existing values - TLS : Only TLS 1.3 is accepted (AEAD cipher suites only, ephemeral key exchange only)
- Credentials : The server key and approved-client information are kept together in the shared RIGDOCKS storage location. They are not removed on uninstall
- Connection limits : Added upper limits on concurrent connections, concurrent unauthenticated connections, message size before authentication, and time allowed until authentication
- OS notifications : OS banner notifications are shown when a client connects, when a connection request is received, and when an unapproved key is rejected or suspicious traffic is detected
- Module availability : Added a mechanism that decides, for each plugin, whether it can be used over external connections
- Rejecting older programs : Unsupported older-generation modules are no longer loaded
- Path restrictions : Protected folders, such as the RIGDOCKS / RIGDOCKS Bridge folders, can no longer be accessed by APIs that handle files.
