The network access and command execution serve the package's stated remote-execution purpose. The user supplies the Iridium address, pairing requires approval on the Iridium page, and the source masks environment secrets and excludes common credential paths from filesystem access.
Static reason
No blocking static signals were detected.
Trigger
The plugin starts when loaded, but it needs a configured Iridium address and obtains a token only after the Iridium approves the pairing request.
Impact
An approved Iridium can run dsh sessions and, by default, remote commands and file operations within the executor's access rules.
Mechanism
It opens a token-authenticated connection to the configured Iridium and handles its process and filesystem requests, while masking environment secrets and excluding common credential paths.
Evidence
$DSH_HOME/remote-iridium/token/<host>$DSH_HOME/remote-iridium/<host>/
Network endpoints3
Configured Iridium host: /v1/internal/pairConfigured Iridium host: /v1/internal/pair/{request}Configured Iridium host: /v1/internal/exec