dsh-web-login
DeepSeek Harness Web GUI 的密码保护：首次运行时设置密码、记住我会话、防暴力破解锁定、审计日志，以及 Harness 设置中的管理页面。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:liyang52520/dsh-web-login#6fbaf4d3e79da14df272ca14f8d6961b963a7438
Web Login 以 dsh-web-login 发布，当前版本为 1.4.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
中文 · English
An independent password gate for the DeepSeek Harness Web GUI.
Zero-dependency Cordis plugin. Takes over / and /index.html: a request that has not passed verification is not forwarded to Harness, and the launch token is not handed out. Harness's own authentication and /api/* are unaffected.
Requires pnpm. dsh does not bundle it; without pnpm the install command fails with pnpm was not found and leaves the profile unchanged.
npm i -g pnpm
dsh plugin --profile web add git+https://github.com/liyang52520/dsh-web-login.git
The package declares dsh.bundle, so dsh registers it under dsh.profile.bundles automatically. No configuration file needs editing.
Restart dsh to load the plugin. Under systemd that is systemctl restart dsh.
Maintenance:
dsh plugin --profile web update dsh-web-login # upgrade
dsh plugin --profile web remove dsh-web-login # uninstall
DSH_HOME must match the running instance (default ~/.dsh). With any other path the command still succeeds, but installs into a different profile and has no effect on the running instance.
Via pnpm:
cd "${DSH_HOME:-$HOME/.dsh}/profiles/web"
pnpm add 'github:liyang52520/dsh-web-login'
grep -q web-login cordis.patch.yml 2>/dev/null || cat >> cordis.patch.yml <<'EOF'
- insert:
- id: web-login
name: dsh-web-login
EOF
Without pnpm, copy the tracked files instead and write the same insert block:
git clone https://github.com/liyang52520/dsh-web-login.git /opt/dsh-web-login
PROFILE="${DSH_HOME:-$HOME/.dsh}/profiles/web"
mkdir -p "$PROFILE/node_modules/dsh-web-login"
git -C /opt/dsh-web-login archive HEAD | tar -x -C "$PROFILE/node_modules/dsh-web-login"
The two mounting methods must not be combined: a bundle and an insert row each produce a web-login entry, and the duplicate id prevents the configuration tree from loading.
dsh prints a one-time setup token at startup:
dsh web-login: setup-token: 7rJfiimRBtBZbZZqbEY3_O6VBO3Te-bA
Where to find it depends on the deployment: journalctl -u dsh under systemd, the terminal for a foreground run, docker logs in a container.
Visit the site, enter the token and set a password.
Once signed in, the gate is managed from Settings → 登录门禁 (Login Gate) inside Harness. A Chinese label is expected at present; see Interface language.
| Action | Effect |
|---|---|
| Change password | Verifies the current password, then sets a new one; rotates the signing key, invalidating sessions on other devices |
| Reset password | Deletes the stored password; every device must run first-run setup again |
| Sign out | Clears this device's session only |
The panel follows Harness's theme setting.
An agent running on the host cannot get past the gate by spoofing Host, and no --trusted-host value changes that: the gate admits a signed cookie bound to the authority, and the Host/Origin fence it consults afterwards sits behind the gate. Letting a local process through is an explicit choice:
- id: web-login
config:
trustDirectLoopback: true
With it on, a request that arrives directly on the loopback socket and carries none of the headers a reverse proxy adds — the configured clientIpHeader, x-real-ip, x-forwarded-for — is treated as already verified. curl http://127.0.0.1:3080/ then returns the application document, and a headless browser opens the interface already signed in: reaching the document is what makes Harness mint its own session, so no token exchange is needed on the agent's side.
It only takes effect once a password exists, so it cannot spend the first-run setup token. It also opens the document route alone: the login form, the account route and the plugin's /__api/* surface still require the cookie.
Three consequences to accept before enabling it:
ssh -L 3080:127.0.0.1:3080 arrives from the host itself, so tunnel users no longer need the password.The narrower alternative is to leave the option off and give the agent the password: POST it to /__login, keep the dsh_gate cookie, and reuse it. A dedicated token on the same loopback rule is a possible future addition.
Configuration is written to the profile's cordis.patch.yml:
- id: web-login
config:
title: My Harness
rememberDays: 7
config is replaced as a whole; unlisted keys keep their defaults.
| Key | Default | Description |
|---|---|---|
enabled | true | Set to false to take over no routes at all |
title | "DeepSeek Harness" | Page title and login page heading |
passwordMinLength | 8 | Minimum password length |
rememberDays | 30 | Session lifetime when "Remember me" is checked |
sessionHours | 12 | Session lifetime otherwise |
maxFailures | 5 | Consecutive failures before a lockout |
lockoutSeconds | 300 | Lockout duration in seconds |
clientIpHeader | "x-real-ip" | Header used to obtain the real client IP; determines what the rate limit counts |
allowLoopbackSetup | false | Allow loopback addresses to set a password without the setup token |
trustDirectLoopback | false | Treat a proxy-free loopback connection as verified; see "Local agents and automation" |
indexHtml | "" | Explicit path to the frontend index.html |
unlockRemoteSettings | true | Allow remote browsers to change settings; see "Settings are read-only" |
pageTheme | "auto" | Login page colour scheme: auto / light / dark |
Harness's Host/Origin check does not cover the hostname in use. On first encountering this, the plugin prints the required configuration and shows the Host Harness actually received:
dsh web-login: 1) 给 dsh 声明这个主机：--trusted-host harness.example
dsh web-login: 2) 让反向代理透传真实 Host 与 Origin：
dsh web-login: proxy_set_header Host $http_host;
dsh web-login: proxy_set_header Origin $http_origin;
Step 1 is always required; step 2 applies only when access goes through a reverse proxy.
Harness permits only loopback browsers to change settings. Access over a loopback address or an SSH tunnel counts as loopback; access from the public internet through a reverse proxy does not, so the settings page is read-only, shows that message, and the welcome notice reappears on every reload.
The plugin treats password-verified remote browsers as loopback by default (unlockRemoteSettings: true), which restores normal settings access. Set it to false to disable that behaviour.
Stop the service, delete the dsh-web-login/state block from $DSH_HOME/.credentials.yaml, and restart. The next visit runs first-run setup again:
dsh-web-login/state: # delete this block and everything under it
kind: grant
payload:
version: 1
algorithm: scrypt
Audit records go to dsh's standard output, one line each, prefixed with dsh web-login: audit. Under systemd:
journalctl -u dsh --no-pager | grep 'dsh web-login: audit'
Event types: password-set, login-ok, login-failed, password-changed, password-change-failed, password-reset, reset-failed, setup-token-failed, lockout, logout, fence-rejected, api-cross-origin-rejected. Failure events carry a running count.
Defended against: scanners, botnets, and third parties who obtain the URL but are not on the network path. Such access sees only the login page and cannot call /api.
Not defended against an on-path eavesdropper: over plain HTTP the password and cookies travel in the clear. This is a limitation of the protocol, not of the plugin. Where possible, an SSH tunnel is preferable to exposing the port, and requires neither a domain nor a certificate:
ssh -N -L 3080:127.0.0.1:3080 user@<server>
# then open http://127.0.0.1:3080/ locally
The port is then not exposed publicly, and the plugin still applies. Other known boundaries:
$DSH_HOME/.credentials.yaml, mode 0600trustDirectLoopback moves the boundary from "who you are" to "how you connected": see "Local agents and automation" for what it gives upAll gate strings are currently Chinese, in the login and setup pages and in the settings panel. An English interface is not implemented; the screenshots above show the Chinese text. pageTheme selects the colour scheme only.
npm test # node:test, no dependencies
Covers password hashing and verification, cookie signing (replay, tampering, cross-host, expiry), rate limiting and per-address lockout isolation, hostname normalisation, configuration validation, and the browser half's module envelope, slot registration and rendered output.
The browser half client.js is a hand-written window.__ModuleLoader__.load envelope. No bundler is required, and its only runtime import is react.
| dsh version | Status |
|---|---|
0.2.0-rc.2 | Verified in production (Linux + nginx) |
0.1.2-rc.1 | Development and testing (macOS) |
The Harness services used are connection.authorizeIndex(), connection.authenticatedUrl() and connection.requestRejection(), plus the webServer exact-route registration and the credentials record API.
MIT © liyang52520