The network and process execution serve the package’s stated remote-executor purpose. The user configures the destination, public HTTP is rejected, and the remote side must approve pairing before the token is stored and the executor connects.
Static reason
No blocking static signals were detected.
Trigger
The plugin starts when loaded, but makes no connection until an Iridium URL is configured; pairing requires approval on the Iridium page.
Impact
An approved Iridium can run sessions and, by default, shell commands within the executor’s configured file access. This is the package’s stated function.
Mechanism
It sends a bearer token to the configured Iridium endpoint and handles the requested remote sessions and commands. The pairing flow displays the executor’s capabilities, and the plugin masks environment values matching common secret names.
Evidence
$DSH_HOME/remote-iridium/token/<iridium-host>
Network endpoints2
User-configured Iridium origin: /api/exec/pairUser-configured Iridium origin: /api/exec (HTTP and WebSocket)