Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
Secure remote access for DeepSeek Harness using Cloudflare Tunnel, password gate, and Feishu notifications.
- Cloudflare Tunnel for encrypted remote access
- Password gate for secure authentication
- Feishu notifications for real-time alerts
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add github:oh-summy/dsh-remote-control#v0.3.1Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| v0.3.1 | ○ | ○ | ○ | ○ | · |
| v0.2.5 | · | · | · | · | ○ |
| v0.1.0 | · | · | · | · | · |
v0.3.1github○ 5 ecosystem plugin2026-10-19
https://github.com/oh-summy/dsh-remote-control
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.3.1
ID: dsh-remote-control-3@v0.3.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-alpha.42026-10-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.3.1
ID: dsh-remote-control-3@v0.3.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.3.1
ID: dsh-remote-control-3@v0.3.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.0-rc.22026-10-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.3.1
ID: dsh-remote-control-3@v0.3.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.3.1
ID: dsh-remote-control-3@v0.3.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.2.5github○ 3 ecosystem plugin2026-10-04
https://github.com/oh-summy/dsh-remote-control
○dsh 0.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.2.5
ID: dsh-remote-control-3@v0.2.5@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.22026-09-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.2.5
ID: dsh-remote-control-3@v0.2.5@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.2.5
ID: dsh-remote-control-3@v0.2.5@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.0github○ 4 ecosystem plugin2026-09-20
https://github.com/oh-summy/dsh-remote-control
○dsh 0.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.1.0
ID: dsh-remote-control-3@v0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.6-alpha.12026-09-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.1.0
ID: dsh-remote-control-3@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.1.0
ID: dsh-remote-control-3@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.22026-09-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/oh-summy/dsh-remote-control#v0.1.0
ID: dsh-remote-control-3@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-remote-control-3/)`Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static medium, dynamic medium — stricter wins → overall medium.
—v0.3.1git2026-10-21v0.3.1same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningcurlDownload · network
bin/status.sh:37CODE_GATE="$(curl -s -o /dev/null -m 5 -w '%{http_code}' "http://$RC_LISTEN/" 2>/dev/null || true)" - warningcurlDownload · network
bin/status.sh:42curl -s -m 5 -c "$JAR" -o /dev/null --data-urlencode "pw=$PW" --data "next=/" "http://$RC_LISTEN/rc-login" - warningcurlDownload · network
bin/status.sh:43CODE_OK="$(curl -s -b "$JAR" -o /dev/null -m 5 -w '%{http_code}' "http://$RC_LISTEN/" 2>/dev/null || true)" - warningnetIp · network
bin/up.sh:272AUTH_CODE="$(curl -s -o /dev/null -m 2 -w '%{http_code}' "http://127.0.0.1:$RC_AUTH_PORT/rc-login" 2>/dev/null)" - warningcurlDownload · network
bin/up.sh:92CODE="$(curl -s -o /dev/null -m 2 -w '%{http_code}' "http://$RC_UPSTREAM/" 2>/dev/null || true)" - warningcurlDownload · network
bin/up.sh:99CODE="$(curl -s -o /dev/null -m 2 -w '%{http_code}' "http://$RC_UPSTREAM/" 2>/dev/null || true)" - warningcurlDownload · network
bin/up.sh:271GATE_CODE="$(curl -s -o /dev/null -m 2 -w '%{http_code}' "http://$RC_LISTEN/" 2>/dev/null)" - warningcurlDownload · network
bin/watchdog.sh:206CODE="$(curl -s -o /dev/null -m 5 -w '%{http_code}' "http://$RC_UPSTREAM/" 2>/dev/null || true)" - warningcurlDownload · network
scripts/install-remote.sh:31FINAL_URL="$(curl -sIL -o /dev/null -w '%{url_effective}' "https://github.com/$REPO/releases/latest" || true)" - warningcurlDownload · network
scripts/install-remote.sh:46curl -fSL --retry 3 -m 120 -o "$TMP_DIR/$PKG_NAME.tar.gz" "$BASE/$PKG_NAME.tar.gz" - warningcurlDownload · network
scripts/install-remote.sh:47curl -fSL --retry 3 -m 60 -o "$TMP_DIR/$PKG_NAME.tar.gz.sha256" "$BASE/$PKG_NAME.tar.gz.sha256" - warningcurlDownload · network
scripts/install.sh:19dl() { curl -fSL --retry 3 -m 300 -o "$2" "$1"; }
show 4 audit findings
- mediumauth-server reads the DSH browser-session secret and mints 7-day signed DSH cookies
bin/auth-server.py:59On startup and on every login the service loads the DSH browser-session signing key from ~/.dsh/.credentials.yaml and uses it (line 127, _dsh_cookie_value) to HMAC-sign a cookie with a 7-day expiry, and in the GET /?token= path it signs whatever authority the client puts in the Host header (line 209). This is a deliberate SSO bridge, but it means the gateway can mint DSH auth cookies without DSH's own consent and holds a cross-application secret in memory for the lifetime of the process; anyone who obtains the gateway password (or the launch token, which is also persisted in logs/run/dsh-token
- lowPassword rotation does not invalidate existing rc_session cookies
scripts/rotate-password.sh:18rotate-password.sh only regenerates the password file and restarts the services; ~/.remote-control/session.secret (the value embedded in every rc_session cookie, with SESSION_TTL = 7*86400 at bin/auth-server.py:31) is left untouched, and /rc-logout only clears the cookie client-side. An attacker who already held a valid cookie or the old password therefore keeps access for up to seven days after the operator rotates the password, contradicting the promise that rotation makes the new password 'take effect'.
- lowPlaintext access password is pushed to Feishu by default
bin/notify-feishu.sh:74With the default RC_NOTIFY_PASSWORD=full, the script sends the full plaintext gateway password to Feishu via lark-cli (or embeds it in the webhook card path). The password therefore leaves the machine and is retained in a third-party chat service and on every device logged into that account; the safer 'mask' mode (last 4 characters) exists but is not the default.
- lowLogin rate-limit key trusts client-supplied X-Forwarded-For
bin/auth-server.py:136client_ip() takes the first element of X-Forwarded-For, i.e. the value most easily supplied by the client, and FAILS is keyed on it. When the gateway is reached without a Cloudflare-set Cf-Connecting-Ip (e.g. RC_LISTEN bound to a LAN/public address, or any deployment where the first hop does not overwrite the header), a client can rotate the header to get a fresh 5-attempt counter and bypass the 300-second lockout on the password form. Impact is limited because generated passwords carry 128 bits of entropy, but the control is not reliable.
Local DSH tunnel/auth orchestrator: no RCE or covert exfiltration found, but it mints DSH session cookies from the DSH secret and sends the password to Feishu by default.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-21 · activity: Active
• Repo created: 2026-08-30
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).