@tonyruan/dsh-bridge-host 0.1.1-beta.6 → 0.1.1-beta.8
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/README.md +16 -10
- package/lib/agent.mjs +213 -213
- package/lib/client.js +426 -428
- package/lib/controller.mjs +106 -106
- package/lib/index.mjs +175 -167
- package/lib/local-management.mjs +8 -7
- package/lib/management.mjs +159 -156
- package/lib/multi-client-profile.mjs +96 -96
- package/lib/multi-client-session.mjs +260 -260
- package/lib/profile-store.mjs +96 -96
- package/lib/session.mjs +261 -261
- package/package.json +3 -3
- package/scripts/prepublish-check.mjs +1 -1
package/README.md
CHANGED
|
@@ -1,12 +1,18 @@
|
|
|
1
|
-
#
|
|
1
|
+
# beta.8: LAN onboarding
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Fresh installations start and pair over LAN without relay configuration. Click Start to initialize and open pairing in one step. Existing identities, pairings and relay configuration are retained.
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
5
|
+
# DSH Bridge host beta
|
|
6
|
+
|
|
7
|
+
A community DSH-compatible phone-access plugin, not an official DeepSeek product. Requires Node.js >=24.9.0 and DSH0.2.2-rc.1.
|
|
8
|
+
|
|
9
|
+
Package: @tonyruan/dsh-bridge-host. Use the official DSH plugin manager for installation; stop the target profile before package-name migration. Cordis ID dsh-phone-access, plugin name phone-access, API routes and existing profileDirectory/identity remain stable. The default profile is the existing .dsh-phone-profile; changing an npm name does not authorize replacing data.
|
|
10
|
+
|
|
11
|
+
This generic build contains no personal relay preset or update root/feed. Without relay configuration, new and existing profiles use LAN-only while preserving their identity and paired devices. Existing saved relay configuration is reused. To retain relay access when replacing an old private code-only preset, use the previously supplied local deployment migration helper before replacing it. LAN-only does not enable diagnostic upload or update networking.
|
|
12
|
+
|
|
13
|
+
Own project code is licensed under the standard PolyForm Noncommercial License1.0.0 in LICENSE. This is not OSI open-source; permitted purposes and exceptions are governed by that exact text, not a blanket promise about every business/payment scenario. Third-party components retain their own permission, copyright and NOTICE terms in THIRD-PARTY-NOTICES.txt and oss-licenses/. These own-code terms do not restrict upstream rights. The complete own development project/Git repository is not included; npm runtime JavaScript is publicly readable. Native platform download assets are not included in this npm release.
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
Beta6/build26 retains the original validated persisted connection realm across upgrades and LAN-only restarts, including previously paired WSS realms without an unused relay leaf. Existing trusted deployment is reused without import or rewrite. AUTO still requires trusted TLS material. Legacy private code-only presets require the separately delivered Linux pre-upgrade migration helper before replacement; it statically validates the original local package and pin, never executes old code or fetches a new network leaf. No identity/pairing/schema reinitialization or client update-source JSON is required.
|
|
17
|
+
|
|
18
|
+
Beta7/build27 fixes the setting sidebar icon through the native settings.section.icon slot, without changing the phone-connection name or the general settings icon. An already-native-authenticated hostname may be used only for independently proven direct LAN sockets; the private internal flag cannot authorize relay, unknown, virtual/VPN or unverified interfaces, or bypass native Cookie/Host/Origin. The UI distinguishes native admission403 from the plugin fixed management403, and both remain blocked. Targeted raw-LAN positives use synthetic interface facts; the actual rc.1 browser/navigation checks use an isolated loopback profile. The real user Ubuntu version and route were not inspected, so site-specific resolution and a real physical-LAN success are not claimed.
|