The source implements a remote-session executor that has no default destination and requires approval on the configured Iridium before pairing. Its broad executor capabilities match the package’s stated purpose, and the inspected credential flow masks secret-like environment values.
Static reason
No blocking static signals were detected.
Trigger
The user configures an Iridium URL; access begins only after the Iridium page approves the displayed pairing code.
Impact
The paired service can use the executor’s intended remote-session and file capabilities, subject to configured roots and denied paths.
Mechanism
Connects to the configured Iridium over HTTPS or permitted private-network HTTP, masks secret-like environment values in its hello message, and handles requests from the paired service.
Evidence
$DSH_HOME/remote-iridium/token/<Iridium-host>$DSH_HOME/remote-iridium/<Iridium-host>/
Network endpoints2
user-configured Iridium origin: /api/exec/pairuser-configured Iridium origin: /api/exec