RADNODZ_ver2.0.0

Runtime moved to RIGDOCKS Bridge

• Resident app : The API processing now runs inside RIGDOCKS Bridge (a resident app)
• Installation : Now installed as a package from RIGDOCKS Bridge
• Settings : Settings and third-party notices moved to the plugin settings screen in RIGDOCKS Bridge
• Signature verification : Code signatures are verified before a module is loaded, and modules that fail verification are not loaded
• Terms of use : APIs cannot be run until the terms of use have been accepted in RIGDOCKS Bridge

Can now be operated from the command-line program "rigcmd"

Server changes

• Single listener : The RIGDOCKS core now handles TCP listening (accepting connections, TLS and routing to the destination). RIGDOCKS as a whole uses a single port, and the listening address and port are managed in RIGDOCKS Bridge
• Default port : The default for new installations changed from 12345 to 23760. Environments with saved settings keep their existing values
• Default listening : On new installations the listening address is 127.0.0.1 (this PC only) and the server is OFF. Whether to expose it externally is up to the user in RIGDOCKS Bridge
• Settings screen : The server is now started and stopped with a toggle on the [plugin settings screen] in RIGDOCKS Bridge. Third-party notices can also be opened from the same screen
• TLS : Only TLS 1.3 is accepted (AEAD cipher suites only, ephemeral key exchange only). Clients using TLS 1.2 or earlier cannot connect
• Credentials : Keys and approved-client information moved to the shared RIGDOCKS storage location. Added a flow where clients request key approval and the request is approved in RIGDOCKS Bridge
• Connection limits : Added upper limits on concurrent connections, concurrent unauthenticated connections, message size before authentication, and time allowed until authentication
• Version check : Client compatibility is now judged by a range of communication-protocol (ABI) versions instead of an exact version ID match. Updates that do not change the protocol no longer require replacing the client. Unsupported versions are rejected with NotSupportedAbiVersion
• Logs : Connection start, end and source are recorded in each product's log. Per-client communication logs (OFF by default) can be enabled from the Server tab in RIGDOCKS Bridge