@fengasdf/dsh-remote-screen2 avatar

@fengasdf/dsh-remote-screen2

Remote Linux desktops in the DSH Web UI: an xrdp RDP session or a live VNC mirror of the console, in draggable multi-windows backed by guacd.

PluginDesktopBrowserStorageWeb search
Verification
L5 · Run tested
Verified
Risk
Medium
Health
Active
Trust
Silver

Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →

Install verification badge dsh 0.2.2-rc.1

Data as of (UTC)

What it doesAI

Brings remote Linux desktops into the DSH Web UI as draggable windows, with xrdp RDP sessions or live VNC console mirrors via guacd.

  • Opens full remote Linux desktops inside the DSH Web UI
  • Supports xrdp RDP sessions and live VNC console mirrors
  • Multi-window layout with draggable windows, backed by guacd
desktopAI

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:fengasdf/dsh-remote-screen2

security scan passed · default branch source

Install method: GitHub · runtime verified (L5)

Verification & Compatibility

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

Declared DSH compatibilityfrom package.json · peerDependencies
package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.2.2-rc.1
current
df202d·
9ab57e✓
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
df202dgithub2026-11-10

https://github.com/fengasdf/dsh-remote-screen2

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

9ab57egithub✓ 1 runtime-verified2026-11-10

https://github.com/fengasdf/dsh-remote-screen2

✓dsh 0.2.2-rc.1current2026-11-10L5 · runtime verified
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.2-rc.1
  • • Plugin artifact: github · https://github.com/fengasdf/dsh-remote-screen2#9ab57e9c94ecc4030d7cc621bd0ebd62ad2d1207
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Passed
Install + runtime smoke verified in the dsh sandbox — installs and runs
L5 · runtime verified · valid for dsh 0.2.2-rc.1

ID: dsh-remote-screen2@9ab57e9c94ecc4030d7cc621bd0ebd62ad2d1207@dsh0.2.2-rc.1 · profile: l4-sandbox

Issued: 2026-11-10 · expires: 2026-11-17

View checks & evidence
L1 · Found✓ Passed

↳ carried from earlier record dsh-remote-screen2@df202d@dsh0.2.2-rc.1 (l3-fullscan)

Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed

↳ carried from earlier record dsh-remote-screen2@df202d@dsh0.2.2-rc.1 (l3-fullscan)

Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed

↳ carried from earlier record dsh-remote-screen2@df202d@dsh0.2.2-rc.1 (l3-fullscan)

Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-11-10
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-11-10
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-10
spec github:fengasdf/dsh-remote-screen2 · channel GitHub source · outcome ran · exit 0
check took: 2.6s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-10
spec github:fengasdf/dsh-remote-screen2 · channel GitHub source · outcome ran · exit 0
check took: 2.6s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-10
spec github:fengasdf/dsh-remote-screen2 · channel GitHub source · outcome ran · exit 0
check took: 2.6s
L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-10
spec github:fengasdf/dsh-remote-screen2 · install mode reused L4 scratch
check took: 289ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-11-10
ready line dsh web: http://127.0.0.1:55477/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-11-10
path / · HTTP 200 · took 289ms
Plugin active in inventory✓ Passed
Source: DSH runtime · Method: plugin inventory query · Captured 2026-11-10
verdict active · entries 150
match: include:remote-screen · dsh-remote-screen · phase active
phases: active 122 · null 28

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-remote-screen2.svg)](https://www.dsh.so/artifact/dsh-remote-screen2/?ref=badge)`
dsh 0.2.2-rc.1 install verified
`[![dsh.so install · dsh 0.2.2-rc.1](https://cdn.dsh.so/badge/install/dsh-remote-screen2@0.2.2-rc.1.svg)](https://www.dsh.so/artifact/dsh-remote-screen2/?ref=badge-install)`

dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.

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.

dsh-remote-screen2Automated review · daily

Static high; dynamic medium (authoritative when present) → overall medium.

static high→dynamic medium→overall medium
dynamic findings0 critical·0 high·1 medium·2 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.0dsh manifest
scanned version0.1.0git2026-11-11
current version0.1.0same version
vet verdictsuspicious · git

Vet is an AST static scan (npm artifact or git source).

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-11-11
audited artifactgit 9ab57e9c94ecc4030d7cc621bd0ebd62ad2d1207
findings0 critical·0 high1 medium / 2 low hidden
show 3 audit findings
  • mediumSetup script exposes unauthenticated guacd and a password-less VNC console mirror to the networkscripts/remote-setup.sh:20

    By default the installer binds guacd on 0.0.0.0:4822 and guacd has no authentication; the same script then starts x11vnc with `-nopw -localhost -rfbport 5900` mirroring the active console (line 55). Anyone who can reach port 4822 can issue a guacd VNC connect to 127.0.0.1:5900 and obtain password-less control of the console desktop, or drive the RDP path to the xrdp login screen, with no plugin-side authentication in between. The risk is documented only in a note printed after the exposure is created.

  • lowWebSocket fragment buffer is unbounded, allowing memory exhaustionlib/ws.js:170

    Single frames are capped at MAX_MESSAGE (32 MB), but a fragmented message has no aggregate limit: a client of /remote-desktop/ws can stream continuation frames and grow this.fragment indefinitely. The pre-handshake `pending` array in lib/guacd-bridge.js has the same unbounded shape. Reachable by any client that completes the upgrade; the effect is host memory exhaustion/OOM.

  • lowWebSocket upgrade skips the Origin check when the header is absent and performs no authentication itselfindex.js:100

    Browsers always send Origin, so cross-site WebSocket hijacking is blocked; but any non-browser client, or a proxy that strips Origin, can open /remote-desktop/ws?machine=<id> and obtain a bridged guacd session. The handler relies entirely on the host web server and network position for authentication, while guacd itself authenticates nothing, so a reachable DSH listener becomes a free tunnel to the configured machines (and to the password-less console mirror if the setup script was run).

No RCE, secret access or exfiltration; risks are the installer's default 0.0.0.0 guacd plus a password-less VNC mirror, an unbounded WebSocket fragment buffer, and an Origin check that passes when the header is absent.

Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.

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-11-06 · activity: Active

• Repo created: 2026-11-06

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/fengasdf/dsh-remote-screen2

Frequently asked questions

What is @fengasdf/dsh-remote-screen2?

@fengasdf/dsh-remote-screen2 is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.

Is dsh.so or this plugin page official?

dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.

How do I install @fengasdf/dsh-remote-screen2?

Run dsh plugin --profile web add github:fengasdf/dsh-remote-screen2 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).

How does the security scan relate to a manual audit?

Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.

How fresh is the data on this page?

The data on this page is as of 2026-11-11 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.

Was this page helpful?