The source implements the advertised remote executor: it contacts a configured Iridium address, waits for pairing approval, and saves the resulting token for that host. The inspected handshake redacts likely secret environment values, and no install hook or unrelated collector was found.
Static reason
No blocking static signals were detected.
Trigger
A user configures an Iridium address in settings or invokes /iridium with an address; first-time pairing also requires approval in the Iridium web page.
Impact
The configured Iridium can use the executor capabilities the user enables and sees the offered system and runtime details. The inspected code redacts likely secret environment values from the handshake.
Mechanism
The plugin pairs with that Iridium, stores its token with restrictive file permissions, then uses the token to relay the Iridium's requested sessions and executor operations.
Evidence
$DSH_HOME/remote-iridium/token/<Iridium-host>$DSH_HOME/remote-iridium/<Iridium-host>/
Network endpoints1
User-configured Iridium HTTPS origin: /v1/internal/pair, /v1/internal/pair/{request}, and /v1/internal/exec (WebSocket)