dsh-auth-remote 0.3.1 → 0.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -1
- package/CHANGELOG.zh-CN.md +12 -1
- package/CONTRIBUTING.md +1 -1
- package/CONTRIBUTING.zh-CN.md +1 -1
- package/README.md +26 -18
- package/README.zh-CN.md +26 -18
- package/dist/cli.js +63 -530
- package/dist/cli.js.map +4 -4
- package/dist/client.js +915 -133
- package/dist/client.js.map +3 -3
- package/dist/index.js +83 -22
- package/dist/index.js.map +3 -3
- package/dist/login.css +0 -21
- package/dist/login.css.map +2 -2
- package/dist/login.js +892 -155
- package/dist/login.js.map +3 -3
- package/dist/types/adapters/dsh/browser-capability.d.ts.map +1 -1
- package/dist/types/adapters/dsh/liveshare.d.ts +4 -0
- package/dist/types/adapters/dsh/liveshare.d.ts.map +1 -0
- package/dist/types/adapters/dsh/webserver.d.ts +8 -4
- package/dist/types/adapters/dsh/webserver.d.ts.map +1 -1
- package/dist/types/cli/ipc-client.d.ts.map +1 -1
- package/dist/types/cli/messages.d.ts +56 -0
- package/dist/types/cli/messages.d.ts.map +1 -0
- package/dist/types/cli/profile.d.ts.map +1 -1
- package/dist/types/cli/prompt.d.ts.map +1 -1
- package/dist/types/index.d.ts.map +1 -1
- package/dist/types/shared/i18n.d.ts +878 -105
- package/dist/types/shared/i18n.d.ts.map +1 -1
- package/dist/types/shared/locales/de.d.ts +145 -0
- package/dist/types/shared/locales/de.d.ts.map +1 -0
- package/dist/types/shared/locales/en.d.ts +0 -49
- package/dist/types/shared/locales/en.d.ts.map +1 -1
- package/dist/types/shared/locales/es.d.ts +145 -0
- package/dist/types/shared/locales/es.d.ts.map +1 -0
- package/dist/types/shared/locales/fr.d.ts +145 -0
- package/dist/types/shared/locales/fr.d.ts.map +1 -0
- package/dist/types/shared/locales/ja.d.ts +145 -0
- package/dist/types/shared/locales/ja.d.ts.map +1 -0
- package/dist/types/shared/locales/pt.d.ts +145 -0
- package/dist/types/shared/locales/pt.d.ts.map +1 -0
- package/dist/types/shared/locales/ru.d.ts +145 -0
- package/dist/types/shared/locales/ru.d.ts.map +1 -0
- package/dist/types/shared/locales/zh.d.ts +0 -49
- package/dist/types/shared/locales/zh.d.ts.map +1 -1
- package/docs/deployment.md +19 -13
- package/docs/deployment.zh-CN.md +19 -13
- package/docs/development.md +39 -28
- package/docs/development.zh-CN.md +39 -28
- package/docs/legacy-compatibility.md +119 -67
- package/docs/legacy-compatibility.zh-CN.md +117 -65
- package/docs/releasing.md +11 -11
- package/docs/releasing.zh-CN.md +11 -11
- package/docs/support-history.md +49 -48
- package/docs/support-history.zh-CN.md +49 -48
- package/examples/web-profile-auth-remote.patch.yml +1 -1
- package/package.json +15 -14
- package/dist/types/cli/language.d.ts +0 -14
- package/dist/types/cli/language.d.ts.map +0 -1
package/CHANGELOG.md
CHANGED
|
@@ -6,9 +6,20 @@ This file records user-visible changes to the released package. Version numbers
|
|
|
6
6
|
|
|
7
7
|
## Unreleased
|
|
8
8
|
|
|
9
|
+
## 0.3.2 - 2026-10-28
|
|
10
|
+
|
|
11
|
+
- Prepare unpublished candidate `0.3.2`, adding DSH `0.2.2-alpha.2` to the original seven exact targets and pinning the development default and manual migration recommendation to it. Retain DSH `>=0.2.1-alpha.3`, forward admission and plugin Node `>=24`. The date records preparation; final same-archive reports are recorded separately.
|
|
12
|
+
- Gate native named/fallback HTTP resources before Fetch conversion while preserving native routing, ETag/HEAD, stream cancellation and in-process peer reads.
|
|
13
|
+
- Isolate LiveShare viewers from the administrator client; restore trusted business Origin only for the two native Owner-login POSTs. Verify basic flows with a local Relay protocol stand-in and keep share/session lifetimes independent; real Relay/OAuth and visitor business operations are outside that verification.
|
|
14
|
+
- Make CLI text fixed English and remove `--lang` and environment-language selection; old language arguments are invalid. Preserve JSON fields, exit codes, confirmation and secret-input contracts.
|
|
15
|
+
- Complete browser English, Chinese, Japanese, Spanish, French, German, Russian and Brazilian Portuguese without expanding old DSH language catalogs. Remove the login language selector; use new `dsh-auth-remote-lang` memory, then `navigator.language`, then English. Remember only native accepted preferences and keep them on sign-out. Ignore, retain and do not migrate old `dsh-auth-remote.locale`.
|
|
16
|
+
- Extend native caching, mux compression/expiry/revocation, host switching, UI and genuine HMR failure/rollback regression while retaining ACCOUNT/HMR, allowedOrigins and shared security checks.
|
|
17
|
+
|
|
18
|
+
- Clean regular build output before emission so deleted modules leave no stale published declarations.
|
|
19
|
+
|
|
9
20
|
## 0.3.1 - 2026-10-28
|
|
10
21
|
|
|
11
|
-
-
|
|
22
|
+
- Publish `0.3.1` for seven exact DSH releases, adding `0.2.1-rc.3` and `0.2.1-rc.4`; use `0.2.1-rc.4` by default and require DSH `>=0.2.1-alpha.3`.
|
|
12
23
|
- Retire six older hosts with plugin `0.2.0` as their last supported plugin. Mark `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5` legacy from 2026-10-28, with earliest retirement eligibility 2026-11-11 (Asia/Shanghai); dates do not automatically stop support.
|
|
13
24
|
|
|
14
25
|
- Remove retired-host-only IPv4/TLS/protocol/public-URL and direct Settings branches. Remove old theme fallbacks and delegate focus color to native rules while retaining shared authentication, Secure, revocation and TLS-failure cleanup. Keep account callback, HMR context and old allowedOrigins configuration migration.
|
package/CHANGELOG.zh-CN.md
CHANGED
|
@@ -6,9 +6,20 @@
|
|
|
6
6
|
|
|
7
7
|
## 未发布
|
|
8
8
|
|
|
9
|
+
## 0.3.2 - 2026-10-28
|
|
10
|
+
|
|
11
|
+
- 准备未发布候选 `0.3.2`,在原七个精确目标外新增 DSH `0.2.2-alpha.2`,并将开发默认与人工迁移推荐固定到该版本。保留 DSH `>=0.2.1-alpha.3`、前向准入和插件 Node `>=24`。日期仅为准备日期,最终同包报告另行记录。
|
|
12
|
+
- 在 Fetch 转换前保护原生 named/fallback HTTP resource,保留原生路由、ETag/HEAD、流取消和进程内 peer 读取。
|
|
13
|
+
- 隔离 LiveShare viewer 与管理员客户端;仅对两个原生 Owner 登录 POST 恢复可信业务 Origin。以本地 Relay 协议替身验证基础流程,分享与插件会话生命周期独立;不宣称真实 Relay/OAuth 或访客业务已验证。
|
|
14
|
+
- CLI 文案固定英语,移除 `--lang` 和环境语言选择;旧语言参数作为无效参数拒绝。JSON 字段、退出码、确认和保密输入合同保持。
|
|
15
|
+
- 浏览器补齐英、中、日、西、法、德、俄和巴西葡语;不扩充旧 DSH 原生语言目录。登录页移除语言选择器,使用新 `dsh-auth-remote-lang` 缓存、`navigator.language`、英文;仅记忆原生表单已接纳的偏好,退出保留。旧 `dsh-auth-remote.locale` 不读取、不清理、不迁移。
|
|
16
|
+
- 扩展新版缓存、原生 mux 压缩/到期/撤销、宿主往返、界面与真实 HMR 故障回滚回归,保留 ACCOUNT/HMR、allowedOrigins 和共享安全检查。
|
|
17
|
+
|
|
18
|
+
- 普通构建先清理输出目录,避免已删除模块遗留陈旧的发布类型声明。
|
|
19
|
+
|
|
9
20
|
## 0.3.1 - 2026-10-28
|
|
10
21
|
|
|
11
|
-
-
|
|
22
|
+
- 发布 `0.3.1`,精确支持七版 DSH,新增 `0.2.1-rc.3`、`0.2.1-rc.4`,默认使用 `0.2.1-rc.4`,要求 DSH `>=0.2.1-alpha.3`。
|
|
12
23
|
- 六个旧宿主退出支持,最后支持插件为 `0.2.0`。`0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5` 自 2026-10-28 转为 legacy,最早退役资格日为 2026-11-11(Asia/Shanghai),日期不会自动停止支持。
|
|
13
24
|
|
|
14
25
|
- 删除退役宿主独占的 IPv4/TLS/协议/公开 URL 与直接 Settings 分支;移除旧主题后备值并委托原生焦点颜色规则,保留共享认证、Secure、撤销和 TLS 失败清理。账号回调、HMR 上下文与旧 allowedOrigins 配置迁移继续保留。
|
package/CONTRIBUTING.md
CHANGED
|
@@ -26,4 +26,4 @@ Create a focused branch from `master`. Include the reason for the change, its us
|
|
|
26
26
|
|
|
27
27
|
The `CI Verify` check runs on pull requests and again after a merge to `master`. A maintainer updates the version and dated changelog entry before creating a release tag. The [release guide](docs/releasing.md) describes that process.
|
|
28
28
|
|
|
29
|
-
|
|
29
|
+
Published `0.3.1` retains its seven-target support and retirement history. The current unpublished candidate is `0.3.2`, declaring eight exact targets; both support policies keep their prior release content. Support/shared-host changes require one final archive across eight complete CLI/browser/smoke targets, following the release guide. Full/releases also require independent `0.2.1-alpha.2` refusal; ordinary runs no real retired-host negative job. The six-host one-time negative acceptance belongs to the `0.3.1` migration history. Never rebuild or pack in the final consumer loop.
|
package/CONTRIBUTING.zh-CN.md
CHANGED
|
@@ -26,4 +26,4 @@ pnpm check
|
|
|
26
26
|
|
|
27
27
|
`CI Verify` 会在 Pull Request 和合入 `master` 后运行。维护者在创建发布标签前更新版本号和带日期的更新日志;具体流程见[发布指南](docs/releasing.zh-CN.md)。
|
|
28
28
|
|
|
29
|
-
|
|
29
|
+
已发布 `0.3.1` 的七版支持和退役事实保留在历史记录;当前未发布候选为 `0.3.2`,声明八个精确目标。两份 support-policy 继续保留此前发布内容。支持或共享宿主变更须按发布指南消费同一最终归档,八版完整 CLI/browser/smoke;full/发布还要求独立 `0.2.1-alpha.2` 退役拒绝,ordinary 不运行真实旧宿主负向。六版一次性负向属于 `0.3.1` 迁移历史。不要在最终消费循环重建或打包。
|
package/README.md
CHANGED
|
@@ -6,13 +6,14 @@ Single-user remote sign-in for DeepSeek Harness (DSH), with password, TOTP, one-
|
|
|
6
6
|
|
|
7
7
|
## Requirements
|
|
8
8
|
|
|
9
|
-
- Linux with `/proc`, Node.js 24 or newer, and one exact DSH target below; development defaults to `0.2.
|
|
9
|
+
- Linux with `/proc`, Node.js 24 or newer, and one exact DSH target below; development defaults to `0.2.2-alpha.2`. pnpm 12.5.1 is needed only when building from source.
|
|
10
|
+
- DSH `0.2.2-alpha.2` itself requires Node.js `>=24.9.0`; the plugin keeps its own `>=24` engine range.
|
|
10
11
|
- DSH's default `~/.dsh` data directory and a `web` profile. The account state belongs to that profile; it is not shared with another profile.
|
|
11
12
|
- For source browser tests, install Playwright Chromium with `pnpm exec playwright install chromium`. The tests use that managed browser and a dedicated, self-signed TLS fixture.
|
|
12
13
|
|
|
13
14
|
## DSH compatibility
|
|
14
15
|
|
|
15
|
-
Unpublished candidate **`0.3.
|
|
16
|
+
Published `0.3.1` retains its seven-host release record. Unpublished candidate **`0.3.2`** declares the eight exact targets below in `dsh.compatibility.dshReleases`. `engines.dsh`, the WebServer peer and runtime admission share the minimum `>=0.2.1-alpha.3`, with no upper bound and SemVer prereleases included. **`0.2.2-alpha.2`** is the development default and migration recommendation. Final same-archive verification is recorded separately from declarations.
|
|
16
17
|
|
|
17
18
|
| Exact supported DSH release | Maintenance | Legacy since | Window | Earliest eligible retirement |
|
|
18
19
|
| --------------------------- | ----------------------------------- | ------------ | ------- | ---------------------------- |
|
|
@@ -22,31 +23,32 @@ Unpublished candidate **`0.3.1`** declares the seven exact targets below in `dsh
|
|
|
22
23
|
| `0.2.1-rc.1` | Normal support | — | — | Not announced |
|
|
23
24
|
| `0.2.1-rc.2` | Normal support | — | — | Not announced |
|
|
24
25
|
| `0.2.1-rc.3` | Normal support | — | — | Not announced |
|
|
25
|
-
| `0.2.1-rc.4` | Normal support
|
|
26
|
+
| `0.2.1-rc.4` | Normal support | — | — | Not announced |
|
|
27
|
+
| `0.2.2-alpha.2` | Normal support; development default | — | — | Not announced |
|
|
26
28
|
|
|
27
29
|
Dates use `Asia/Shanghai` at 00:00; eligibility never automatically ends support or removes CI. Plugin `0.3.1` retires DSH `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`. Their last supported plugin is published `0.2.0`; this candidate cannot be installed on them. Query [DSH → plugin](docs/support-history.md#by-dsh) or [plugin → DSH](docs/support-history.md#by-plugin) for historical declarations, reports and distribution facts. Both support policies retain the previous release's record; this README and the history describe this candidate.
|
|
28
30
|
|
|
29
|
-
All
|
|
31
|
+
All eight use the same entry configuration and support concrete IPv4/IPv6, native HTTP/HTTPS and CLI `--public-url`. The final public root appears in model runtime context and `DSH_WEB_URL`. Model Web sections must not duplicate that URL or leak a token. The [compatibility inventory](docs/legacy-compatibility.md) records native capabilities and retained adaptations.
|
|
30
32
|
|
|
31
|
-
Later versions are forward-admitted subject to WebServer/Connection APIs, host package identity and native authentication exchange; admission is not an exact support or test claim. Every plan keeps
|
|
33
|
+
Later versions are forward-admitted subject to WebServer/Connection APIs, host package identity and native authentication exchange; admission is not an exact support or test claim. Every plan keeps eight-version CLI/smoke. Full, manual, scheduled and release plans run eight complete browser targets plus independent refusal verification on retired boundary `0.2.1-alpha.2`. Ordinary low-risk plans use the [fixed browser selection](docs/development.md#ordinary-and-full-ci-plans) and run no real retired-host negative job.
|
|
32
34
|
|
|
33
|
-
## Install
|
|
35
|
+
## Install the candidate archive
|
|
34
36
|
|
|
35
|
-
`0.3.
|
|
37
|
+
`0.3.2` is unpublished. Build and verify its local archive using the [development guide](docs/development.md), then install that archive. Published `0.3.1` retains its historical seven-host support and does not provide this new-host adaptation.
|
|
36
38
|
|
|
37
39
|
```sh
|
|
38
40
|
dsh --version
|
|
39
|
-
dsh plugin --profile web add dsh-auth-remote
|
|
41
|
+
dsh plugin --profile web add ./artifacts/dsh-auth-remote-0.3.2.tgz
|
|
40
42
|
dsh plugin --profile web list
|
|
41
43
|
```
|
|
42
44
|
|
|
43
|
-
Check that `dsh --version` prints the recommended `0.2.
|
|
45
|
+
Check that `dsh --version` prints the recommended `0.2.2-alpha.2` and the plugin list includes `dsh-auth-remote@0.3.2`. These commands use DSH's default data directory. For an isolated development runtime, see the [development guide](docs/development.md).
|
|
44
46
|
|
|
45
47
|
## Configure the web profile
|
|
46
48
|
|
|
47
49
|
The minimal setup needs no profile patch. Start with `dsh web --no-open --port 13090` and use the printed `http://127.0.0.1:13090/` root. Without an explicit `publicUrl`, the plugin derives one root from the actual listener protocol, address and bound port, including `--port 0`. Unauthenticated navigation redirects to sign-in. Check `/auth-remote/ready` before relying on the service. Startup prints the listener and one distinct public root, without a native `?token=` URL.
|
|
48
50
|
|
|
49
|
-
For a public HTTPS entry, use the [deployment guide](docs/deployment.md) and [profile example](examples/web-profile-auth-remote.patch.yml), with top-level `publicUrl: https://dsh.example.com/`, `host` and `port`. All
|
|
51
|
+
For a public HTTPS entry, use the [deployment guide](docs/deployment.md) and [profile example](examples/web-profile-auth-remote.patch.yml), with top-level `publicUrl: https://dsh.example.com/`, `host` and `port`. All eight supported versions also support concrete IPv6 and paired top-level `tlsCert`/`tlsKey`. The URL must be an HTTP(S) root, with no credentials, child path, query or fragment. One public origin plus literal loopback is admitted. Setting a URL does not configure proxy routing or TLS.
|
|
50
52
|
|
|
51
53
|
The plugin automatically declares its finalized native bridge authority in Connection's `trustedHosts`, so downstream plugins can recognize a concrete listener without an extra `--trusted-host`. If a downstream route needs the original public Host, add its path to `preserveOriginPaths`; the final public authority is then declared as well. Explicit CLI trusted hosts are retained, while the outer public-origin and sign-in checks still apply. CLI host/port and public URL override file values; TLS overrides as one complete pair. See the [migration and path rules](docs/deployment.md#configuration-priority-and-path-bases) before upgrading `allowedOrigins`: zero or one item is migrated in memory with a warning, multiple items and any explicit coexistence with `publicUrl` fail.
|
|
52
54
|
|
|
@@ -55,7 +57,7 @@ The plugin automatically declares its finalized native bridge authority in Conne
|
|
|
55
57
|
Run this in a real terminal against the **same** default `web` profile as the service:
|
|
56
58
|
|
|
57
59
|
```sh
|
|
58
|
-
dsh plugin --profile web exec dsh-auth-remote init
|
|
60
|
+
dsh plugin --profile web exec dsh-auth-remote init
|
|
59
61
|
```
|
|
60
62
|
|
|
61
63
|
Enter one username and a password of 12–256 Unicode characters. The password is not a command-line argument and is not echoed. The login page guides an uninitialized profile back to this command; it cannot create the account. TOTP is optional by default (`requireTotp: false`); the first password sign-in offers setup or skipping it. Set `requireTotp: true` to require setup. Upgrading follows the new default only when no explicit policy is configured; existing TOTP bindings, backup codes and explicit true/false settings are preserved. Save the ten backup codes when shown: each works once and the list cannot be retrieved later.
|
|
@@ -64,32 +66,38 @@ Enter one username and a password of 12–256 Unicode characters. The password i
|
|
|
64
66
|
|
|
65
67
|
Open the direct loopback URL for the minimal installation. After configuring a public origin, open `https://dsh.example.com/auth-remote/login`. Security settings inside DSH can change the password, bind or disable TOTP when policy permits, and revoke sessions. Password or factor changes revoke existing sessions. Sessions have a fixed default lifetime of 168 hours and survive service restarts.
|
|
66
68
|
|
|
67
|
-
On all
|
|
69
|
+
On all eight supported versions, open the sidebar account menu, then **Settings → Security & sign-in**.
|
|
68
70
|
|
|
69
71
|
The sign-in page references DSH's PWA manifest. The manifest and favicons are readable before sign-in; business pages and APIs still require authentication. See the [public resource rules](docs/deployment.md#source-and-bridge-contract).
|
|
70
72
|
|
|
71
73
|
```sh
|
|
72
74
|
dsh plugin --profile web exec dsh-auth-remote status --json
|
|
73
|
-
dsh plugin --profile web exec dsh-auth-remote reset-password
|
|
74
|
-
dsh plugin --profile web exec dsh-auth-remote reset-totp
|
|
75
|
-
dsh plugin --profile web exec dsh-auth-remote revoke-sessions
|
|
75
|
+
dsh plugin --profile web exec dsh-auth-remote reset-password
|
|
76
|
+
dsh plugin --profile web exec dsh-auth-remote reset-totp
|
|
77
|
+
dsh plugin --profile web exec dsh-auth-remote revoke-sessions
|
|
76
78
|
```
|
|
77
79
|
|
|
78
80
|
Mutating commands require an interactive confirmation. Online commands use a private Unix socket; offline commands acquire the same profile lock. If a management response is lost after submission, check `status` before deciding whether to try again. `status --json` keeps its machine-readable keys regardless of language.
|
|
79
81
|
|
|
80
|
-
The embedded Security page follows DSH's language setting.
|
|
82
|
+
The embedded Security page follows DSH's language setting. Browser text supports English, Chinese, Japanese, Spanish, French, German, Russian and Brazilian Portuguese. The standalone login page uses `localStorage["dsh-auth-remote-lang"]`, then `navigator.language`, then English; it has no language selector. Supported language tags match case-insensitively, including regions; invalid or unsupported values fall through to the next choice. The plugin leaves DSH's own language picker unchanged. After entering DSH, only the native locale form's accepted preference updates this memory; clearing the preference removes it. Loading or failed reads/saves leave it intact, and signing out keeps it. The old `dsh-auth-remote.locale` key is ignored and left untouched. CLI text is always English; locale environment variables do not change it, and `--lang` is no longer accepted.
|
|
81
83
|
|
|
82
84
|
Security & sign-in shows the plugin username, TOTP status, this session’s sign-in and expiry times, and active session count. Dates follow the current UI language and browser time zone. Password and TOTP setup/rebind/disable each open a task dialog; enforced TOTP cannot be disabled. Signing out the current session needs confirmation and preserves other sessions. Signing out all sessions verifies the password and any bound second factor, and includes the current session. Security changes revoke all sessions. Successful setup shows backup codes once as the final step of the same dialog, with Copy all and an acknowledgement before signing in again. Escape, the backdrop and parent Settings cannot dismiss this step; leaving or refreshing loses it.
|
|
83
85
|
|
|
84
86
|
## Sign in to an official DeepSeek account
|
|
85
87
|
|
|
86
|
-
Manual callbacks are forward-admitted from `>=0.2.1-alpha.3` using SemVer with prereleases included, and require native capabilities plus `manualAccountLogin: true`. Full feature verification targets **0.2.1-alpha.3**, **0.2.1-alpha.4**, **0.2.1-alpha.5**, **0.2.1-rc.1**, **0.2.1-rc.2**, **0.2.1-rc.3** and **0.2.
|
|
88
|
+
Manual callbacks are forward-admitted from `>=0.2.1-alpha.3` using SemVer with prereleases included, and require native capabilities plus `manualAccountLogin: true`. Full feature verification targets **0.2.1-alpha.3**, **0.2.1-alpha.4**, **0.2.1-alpha.5**, **0.2.1-rc.1**, **0.2.1-rc.2**, **0.2.1-rc.3**, **0.2.1-rc.4** and **0.2.2-alpha.2**; future releases need exact regression before being called verified. In its account menu, **Sign in** first opens an instruction dialog; it does not start authorization immediately. Click **Open sign-in page** to open the official page in a new tab. After approval, that tab may show a connection error or 404 at a loopback address. Copy its entire address, including `code` and `state`, paste it into **Full callback address**, and click **Confirm sign-in**. Keep the original DSH page open throughout. If the popup is blocked, use the dialog's authorization link.
|
|
87
89
|
|
|
88
90
|
In **Settings → Security & sign-in → Sign-in preferences**, the remote DeepSeek sign-in switch defaults to on. Native Settings saves it to the current profile override; new authorizations on this page use the accepted value immediately and restarts preserve it. Failed saves show an error. Turning it off restores native entries for new attempts, preserves admitted manual attempts and existing official-account credentials, and does not establish native public-callback support. Other open pages need no active synchronization; a stale page starting authorization receives disabled feedback and advice to refresh.
|
|
89
91
|
|
|
90
92
|
This manual handoff needs no local listener, SSH tunnel or browser extension. The loopback address is an authorization return address; its page does not need to load. The plugin parses the pasted URL and delivers the callback inside DSH, retaining native state validation, PKCE exchange and credential storage. It never fetches the pasted address. Pending authorization belongs to the initiating remote session, lasts at most ten minutes and is cancelled when dismissed or the session is revoked. Expired or failed authorization must be restarted.
|
|
91
93
|
|
|
92
|
-
On DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3` and `0.2.
|
|
94
|
+
On DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2`, the dialog also offers **Use API key** before authorization begins. It opens the native credential editor and continues setup until the key is saved or the user chooses to defer. The same option is available from the account menu. During active authorization, the secondary button cancels that attempt instead.
|
|
95
|
+
|
|
96
|
+
## LiveShare basic compatibility
|
|
97
|
+
|
|
98
|
+
On DSH `0.2.2-alpha.2`, enable LiveShare, configure its Relay and sign in as Owner through DSH's native setup first. This plugin does not enable sharing or rewrite Relay configuration. Administrator sign-in and share viewers retain separate identities and transports. Signing out of this plugin does not stop existing shares; use native LiveShare management to stop them.
|
|
99
|
+
|
|
100
|
+
Local verification covers the real Host, Owner PKCE flow, share worker, viewer page and stopping shares, with a local protocol stand-in for Relay identity/transport. It does not establish real Relay/OAuth, visitor model calls or file-write experience.
|
|
93
101
|
|
|
94
102
|
## Put a proxy in front
|
|
95
103
|
|
package/README.zh-CN.md
CHANGED
|
@@ -6,13 +6,14 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
|
|
|
6
6
|
|
|
7
7
|
## 前置条件
|
|
8
8
|
|
|
9
|
-
- Linux(含 `/proc`)、Node.js 24 或更高版本,以及下表某个精确 DSH 目标;开发默认 `0.2.
|
|
9
|
+
- Linux(含 `/proc`)、Node.js 24 或更高版本,以及下表某个精确 DSH 目标;开发默认 `0.2.2-alpha.2`。仅从源码构建时需要 pnpm 12.5.1。
|
|
10
|
+
- DSH `0.2.2-alpha.2` 自身要求 Node.js `>=24.9.0`;插件自身仍保持 `>=24` 引擎范围。
|
|
10
11
|
- DSH 默认的 `~/.dsh` 数据目录和 `web` profile。账号状态属于该 profile,不与其他 profile 共用。
|
|
11
12
|
- 源码浏览器测试先执行 `pnpm exec playwright install chromium`。测试使用 Playwright 管理的浏览器和专用自签 TLS 夹具。
|
|
12
13
|
|
|
13
14
|
## DSH 兼容性
|
|
14
15
|
|
|
15
|
-
|
|
16
|
+
已发布 `0.3.1` 保留原有七版发布记录。未发布候选 **`0.3.2`** 在 `dsh.compatibility.dshReleases` 声明以下八个精确目标。`engines.dsh`、WebServer peer 和运行时准入下限一致为 `>=0.2.1-alpha.3`,不设上限且按 SemVer 包含预发布。开发默认与迁移推荐为 **`0.2.2-alpha.2`**。最终同包验证记录与声明分开保存。
|
|
16
17
|
|
|
17
18
|
| 精确支持的 DSH 版本 | 维护状态 | Legacy 起算 | 窗口 | 最早退役资格日 |
|
|
18
19
|
| ------------------- | ------------------ | ----------- | ----- | -------------- |
|
|
@@ -22,31 +23,32 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
|
|
|
22
23
|
| `0.2.1-rc.1` | 正常支持 | — | — | 未公告 |
|
|
23
24
|
| `0.2.1-rc.2` | 正常支持 | — | — | 未公告 |
|
|
24
25
|
| `0.2.1-rc.3` | 正常支持 | — | — | 未公告 |
|
|
25
|
-
| `0.2.1-rc.4` |
|
|
26
|
+
| `0.2.1-rc.4` | 正常支持 | — | — | 未公告 |
|
|
27
|
+
| `0.2.2-alpha.2` | 正常支持;开发默认 | — | — | 未公告 |
|
|
26
28
|
|
|
27
29
|
日期按 `Asia/Shanghai` 当日 00:00 计算;资格日不自动终止支持或删除 CI。插件 `0.3.1` 退役 DSH `0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1`、`0.2.0-rc.2`、`0.2.1-alpha.1`、`0.2.1-alpha.2`,这些宿主最后支持的插件为已发布 `0.2.0`,不能安装本候选。按[DSH → 插件](docs/support-history.zh-CN.md#by-dsh)或[插件 → DSH](docs/support-history.zh-CN.md#by-plugin)查询历史声明、报告与分发事实;两份支持规范保留前一发布的记录,本候选事实以本文和历史表为准。
|
|
28
30
|
|
|
29
|
-
|
|
31
|
+
八版均使用同一入口配置,支持具体 IPv4/IPv6、原生 HTTP/HTTPS、CLI `--public-url`,最终公开根地址写入模型运行时上下文与 `DSH_WEB_URL`。模型 Web 提示各段不应重复公开 URL 或泄露 token。原生能力与保留适配见[兼容维护清单](docs/legacy-compatibility.zh-CN.md)。
|
|
30
32
|
|
|
31
|
-
后续版本按范围向前准入,仍须通过 WebServer/Connection API
|
|
33
|
+
后续版本按范围向前准入,仍须通过 WebServer/Connection API、宿主包身份和原生认证交换检查;准入不构成逐版支持或实测声明。八版始终运行 CLI/smoke,全量、手动、定时及发布计划运行八版完整 browser,并独立验证退役边界 `0.2.1-alpha.2` 的拒绝路径。普通低风险计划使用[固定 browser 选择](docs/development.zh-CN.md#普通与全量-ci-计划),不运行真实旧宿主负向任务。
|
|
32
34
|
|
|
33
|
-
##
|
|
35
|
+
## 安装候选归档
|
|
34
36
|
|
|
35
|
-
`0.3.
|
|
37
|
+
`0.3.2` 尚未发布。先按[开发指南](docs/development.zh-CN.md)构建并验证本地归档,再安装该文件。已发布 `0.3.1` 保留历史七版支持,不包含本次新版宿主适配。
|
|
36
38
|
|
|
37
39
|
```sh
|
|
38
40
|
dsh --version
|
|
39
|
-
dsh plugin --profile web add dsh-auth-remote
|
|
41
|
+
dsh plugin --profile web add ./artifacts/dsh-auth-remote-0.3.2.tgz
|
|
40
42
|
dsh plugin --profile web list
|
|
41
43
|
```
|
|
42
44
|
|
|
43
|
-
确认 `dsh --version` 输出推荐的 `0.2.
|
|
45
|
+
确认 `dsh --version` 输出推荐的 `0.2.2-alpha.2`,且插件列表中有 `dsh-auth-remote@0.3.2`。这些命令使用 DSH 默认数据目录;隔离开发运行时参见[开发指南](docs/development.zh-CN.md)。
|
|
44
46
|
|
|
45
47
|
## 配置 web profile
|
|
46
48
|
|
|
47
49
|
最小安装无需修改 profile 补丁。用 `dsh web --no-open --port 13090` 启动,使用终端打印的 `http://127.0.0.1:13090/` 根地址。未显式设置 `publicUrl` 时,插件根据监听的实际协议、地址和绑定端口生成唯一根地址,包含 `--port 0` 的实际结果。未登录导航跳转登录页;使用服务前检查 `/auth-remote/ready`。启动输出包含监听地址和一个不同的公开根地址,不含原生 `?token=` URL。
|
|
48
50
|
|
|
49
|
-
公网 HTTPS 入口请使用[部署指南](docs/deployment.zh-CN.md)和 [profile 示例](examples/web-profile-auth-remote.patch.yml),设置顶层 `publicUrl: https://dsh.example.com/`、`host`、`port
|
|
51
|
+
公网 HTTPS 入口请使用[部署指南](docs/deployment.zh-CN.md)和 [profile 示例](examples/web-profile-auth-remote.patch.yml),设置顶层 `publicUrl: https://dsh.example.com/`、`host`、`port`。全部八个支持版本还支持具体 IPv6 和成对的顶层 `tlsCert`/`tlsKey`。URL 必须是 HTTP(S) 根地址,不能带凭据、子路径、查询或片段。准入范围是唯一公开来源加字面回环。配置 URL 不会配置代理路由或 TLS。
|
|
50
52
|
|
|
51
53
|
插件自动将定稿的原生桥接 authority 登记到 Connection 的 `trustedHosts`,下游插件无需额外 `--trusted-host` 即可识别具体监听地址。下游路由若需要原始公网 Host,可把路径加入 `preserveOriginPaths`,此时也自动登记最终公开 authority。显式 CLI trusted hosts 继续保留,外层公开来源与登录校验仍然生效。CLI 的 host/port 和公开 URL 覆盖文件值;TLS 按完整一对覆盖。升级 `allowedOrigins` 前阅读[迁移和路径规则](docs/deployment.zh-CN.md#配置优先级与路径基准):零项或单项在内存迁移并告警,多项及任意显式新旧字段共存报错。
|
|
52
54
|
|
|
@@ -55,7 +57,7 @@ dsh plugin --profile web list
|
|
|
55
57
|
在真实交互终端中,使用与服务**相同**的默认 `web` profile:
|
|
56
58
|
|
|
57
59
|
```sh
|
|
58
|
-
dsh plugin --profile web exec dsh-auth-remote init
|
|
60
|
+
dsh plugin --profile web exec dsh-auth-remote init
|
|
59
61
|
```
|
|
60
62
|
|
|
61
63
|
输入一个用户名和 12–256 个 Unicode 字符的密码。密码不作为命令行参数传递,也不会回显。未初始化时登录页会提示该命令,但网页不能创建账号。默认 `requireTotp: false`,首次密码登录可选择绑定或跳过;设为 `true` 可强制绑定。升级仅在未显式配置时采用新默认值,已有 TOTP、备用码与显式 true/false 均保留。显示十个备用码时立即妥善保存:每个只能用一次,之后不能重新查看列表。
|
|
@@ -64,32 +66,38 @@ dsh plugin --profile web exec dsh-auth-remote init --lang zh
|
|
|
64
66
|
|
|
65
67
|
最小化安装时访问本机回环地址;配置公网入口后访问 `https://dsh.example.com/auth-remote/login`。DSH 内的安全设置可以修改密码、绑定 TOTP、在策略允许时关闭 TOTP,以及撤销会话。密码或第二因素变更会撤销已有会话。会话默认固定有效 168 小时,服务重启后仍保留。
|
|
66
68
|
|
|
67
|
-
|
|
69
|
+
全部八个支持版本从侧栏账号菜单进入 **设置 → 安全与登录**。
|
|
68
70
|
|
|
69
71
|
登录页引用 DSH 的 PWA manifest,manifest 与 favicon 在登录前即可读取;业务页面和 API 仍需认证。具体范围见[公开资源规则](docs/deployment.zh-CN.md#来源与桥接契约)。
|
|
70
72
|
|
|
71
73
|
```sh
|
|
72
74
|
dsh plugin --profile web exec dsh-auth-remote status --json
|
|
73
|
-
dsh plugin --profile web exec dsh-auth-remote reset-password
|
|
74
|
-
dsh plugin --profile web exec dsh-auth-remote reset-totp
|
|
75
|
-
dsh plugin --profile web exec dsh-auth-remote revoke-sessions
|
|
75
|
+
dsh plugin --profile web exec dsh-auth-remote reset-password
|
|
76
|
+
dsh plugin --profile web exec dsh-auth-remote reset-totp
|
|
77
|
+
dsh plugin --profile web exec dsh-auth-remote revoke-sessions
|
|
76
78
|
```
|
|
77
79
|
|
|
78
80
|
修改命令需要交互确认。在线命令走私有 Unix socket;离线命令取得同一 profile 锁。如果管理请求已提交但响应丢失,先运行 `status` 再判断是否重试。`status --json` 的机器字段不随语言变化。
|
|
79
81
|
|
|
80
|
-
内嵌安全页跟随 DSH
|
|
82
|
+
内嵌安全页跟随 DSH 语言设置。浏览器文案支持英、中、日、西、法、德、俄和巴西葡萄牙语。独立登录页依次使用 `localStorage["dsh-auth-remote-lang"]`、`navigator.language`、英文,不提供语言选择器;支持的合法语言标签忽略大小写并匹配地区变体;非法或不支持的值依次回退。插件不扩充 DSH 自身的语言选择目录。进入 DSH 后仅按原生 locale 表单已接纳的偏好更新缓存,明确清除偏好时删除缓存;加载中、读取或保存失败时保留,退出也保留。旧 `dsh-auth-remote.locale` 字段不读取、不清理。CLI 文案固定英语;语言环境变量不会改变输出,`--lang` 不再接受。
|
|
81
83
|
|
|
82
84
|
安全与登录页面展示本插件用户名、TOTP 状态、本次登录时间、到期时间和有效会话数;时间按当前界面语言及浏览器本地时区显示。修改密码、开启/重新绑定/关闭 TOTP 均在独立任务弹窗完成;强制策略不允许关闭 TOTP。退出当前会话只需确认且保留其他会话,退出所有会话需验证密码及已绑定的第二因素,并包含当前会话。安全修改会撤销所有会话;绑定成功的同一弹窗最后一步仅展示一次备用码,支持复制全部,确认保存后重新登录。此步骤不能用 Esc、遮罩或父设置关闭;离开或刷新后无法恢复。
|
|
83
85
|
|
|
84
86
|
## 登录 DeepSeek 官方账号
|
|
85
87
|
|
|
86
|
-
手动回填按 SemVer(包含预发布)从 `>=0.2.1-alpha.3` 前向准入,还须具备必要原生 API 且 `manualAccountLogin: true`。完整功能实测目标为 **0.2.1-alpha.3**、**0.2.1-alpha.4**、**0.2.1-alpha.5**、**0.2.1-rc.1**、**0.2.1-rc.2**、**0.2.1-rc.3**、**0.2.1-rc.4**;未来版本须精确回归后才宣称已验证。账号菜单中的“登录”先打开步骤说明弹窗,不会立即发起授权。点击“打开登录页”,在新标签页完成官方登录;授权后该标签页可能在回环地址显示连接失败或 404。复制地址栏中的完整 URL(包含 `code` 和 `state`),粘贴到“完整回调地址”,再点击“确认登录”。整个过程中保留原 DSH 页面;弹窗被浏览器拦截时,可使用弹窗内的授权链接。
|
|
88
|
+
手动回填按 SemVer(包含预发布)从 `>=0.2.1-alpha.3` 前向准入,还须具备必要原生 API 且 `manualAccountLogin: true`。完整功能实测目标为 **0.2.1-alpha.3**、**0.2.1-alpha.4**、**0.2.1-alpha.5**、**0.2.1-rc.1**、**0.2.1-rc.2**、**0.2.1-rc.3**、**0.2.1-rc.4**、**0.2.2-alpha.2**;未来版本须精确回归后才宣称已验证。账号菜单中的“登录”先打开步骤说明弹窗,不会立即发起授权。点击“打开登录页”,在新标签页完成官方登录;授权后该标签页可能在回环地址显示连接失败或 404。复制地址栏中的完整 URL(包含 `code` 和 `state`),粘贴到“完整回调地址”,再点击“确认登录”。整个过程中保留原 DSH 页面;弹窗被浏览器拦截时,可使用弹窗内的授权链接。
|
|
87
89
|
|
|
88
90
|
在 **设置 → 安全与登录 → 登录配置** 中切换“远程 DeepSeek 账号登录”,默认开启。保存通过原生 Settings 写入当前 profile override,当前页新授权立即采用最新值,重启后保留;保存失败会显示错误。关闭只恢复新授权的原生入口,不取消已接纳的手动授权、不退出已有官方账号,也不承诺原生公网回调可用。其他已打开页面无需主动同步;旧页新建授权会提示关闭并建议刷新。
|
|
89
91
|
|
|
90
92
|
手动回填无需本地监听器、SSH 隧道或浏览器扩展。回环地址用于承载授权结果,页面无需正常打开。插件只解析粘贴的 URL,在 DSH 内部分发回调,保留原生 state 校验、PKCE 兑换与凭据存储,不会请求粘贴的地址。待完成授权绑定发起操作的远程会话,最长有效期为十分钟;关闭弹窗或撤销该会话会取消待完成授权。过期或失败后须重新开始。
|
|
91
93
|
|
|
92
|
-
DSH `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4` 的弹窗在授权开始前也提供“使用 API Key”,点击后进入原生凭据编辑器,直到保存密钥或用户选择“稍后配置”才结束引导;账号菜单中也保留同一入口。授权进行中时,次要按钮用于取消本次授权。
|
|
94
|
+
DSH `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.2-alpha.2` 的弹窗在授权开始前也提供“使用 API Key”,点击后进入原生凭据编辑器,直到保存密钥或用户选择“稍后配置”才结束引导;账号菜单中也保留同一入口。授权进行中时,次要按钮用于取消本次授权。
|
|
95
|
+
|
|
96
|
+
## LiveShare 基础兼容
|
|
97
|
+
|
|
98
|
+
在 DSH `0.2.2-alpha.2` 中先按原生方式启用 LiveShare、配置 Relay 并完成 Owner 身份登录;本插件不会自动启用分享或改写 Relay 配置。管理员登录与分享查看者使用各自的身份和传输,退出本插件会话不会停止已创建的分享;停止分享仍由原生 LiveShare 管理。
|
|
99
|
+
|
|
100
|
+
本地验证覆盖真实 Host、Owner PKCE 流程、分享 worker、查看页和停止分享,Relay 身份/传输使用本地协议替身。真实 Relay/OAuth、访客模型调用及文件写入体验不属于这些验证结论。
|
|
93
101
|
|
|
94
102
|
## 接入反向代理
|
|
95
103
|
|