DBX fork Linux CLI + MCP: selected TLS-mode repair (2026-10-03)

DBX fork Linux CLI + MCP: selected encrypted TLS-mode repair

Verified Ubuntu 22.04 x86_64 service binaries from the complete retained fork source at 5dd45e85f0a072cac9564acdcef2e9f178dd5be1. Package version remains 0.4.102; identify this build by the commit and hashes below. Both CLI and MCP binaries changed in this build.

New correction

An explicit PostgreSQL URL parameter can select a TLS mode independently of the saved Boolean flag. The new opt-in postgres_sslmode_cas route-plan member supports exactly expected: verify-full, replacement: disable, when the Boolean flag is already false and the route and password inputs are unchanged (fork draft #3, upstream feature #11006).

This mode requires the selected encrypted value to equal the single canonical parameter exactly. Additional parameters, duplicate or conflicting modes, aliases, encoded variants, plaintext copies, wrong keys and stale expectations fail without writes. Preview decrypts and validates only that selected value; apply changes only its encrypted row in the existing transaction and skips the connection-JSON update. Reports contain no parameter contents, SSH passwords or database passwords. Ordinary route operations preserve their previous behavior when the optional mode is omitted. Existing scope, tool-policy and read-only checks remain enforced.

The full prior fork stack is retained: authenticated remote MCP and isolated bounded SSE admission, selected SSH-route import and same-ID route updates, precise persistent-ID allowlists, strict port typing, earlier CLI/MCP and safe-import changes, and the upstream-only mirror guard. Normal package defaults, MQ admin and DuckDB-sidecar support remain enabled. Session work is reviewed in upstream draft #10841.

Contents and verification

The complete archive has five regular files: bin/dbx, bin/dbx-mcp, BUILD_INFO.json, SHA256SUMS and the original Apache-2.0 license. It includes no profiles, credentials, keys, selected-export helper or host configuration. External driver/plugin sidecars remain separate dependencies.

Both stripped binaries were built and exercised in Ubuntu 22.04.5 x86_64, require glibc symbols up to 2.34, and link libc, libm, libgcc_s and the Linux loader.

• 79 focused source tests passed, zero failed; one pre-existing external MongoDB test ignored
• TLS-only checks prove only the selected URL-parameter ciphertext changes; raw connection JSON, stored settings and unrelated ciphertext remain byte-identical. Wrong-key, stale-value, scope and transaction-failure cases leave storage unchanged
• Final route/import, HTTP 32-stream plus 80-tool-call, DELETE cleanup, two stdio-protocol 28-tool, selected-export bridge and ABI checks passed
• The unchanged workflow/mirror-guard files retain their preceding 12/12 contract-test result
• These focused synthetic checks do not constitute a full workspace pass or live production database/provider/ingress validation

Archive SHA-256: 277c84fb98347c7f49db703c34d2a25154748894f3dbe417cf0450fef1edfc7e

Canonical source SHA-256: 52b22834777e5b8f5e60e6a7465b0aafb69f4de17737a0856f0470ec0218af5a across 6,311 files. The exact digest definition and build details are in BUILD_INFO.json.

Optional smaller transfers

Two separate BSDIFF40 asset sets can reconstruct these binaries from their exact preceding-release versions. Each includes a Python-standard-library applier, metadata and a checksum manifest; the complete archive is also available.

• CLI base SHA-256: 4787e3806e4e1ec0d17799b60a56d035cf2ba2e5a0622beb48ffe2ffddc123ad
• CLI delta: 2,088,538 bytes; SHA-256 5728e6433a952737f8a647bd713831274ef218cf44bae26c119acbf7f19639ce
• New CLI SHA-256: bdf53318258c8fac97ec993823856f7120a6205a30792f74c3a853df684d2e58
• MCP base SHA-256: 5ab4f780e2b2da3f4fe722f80295231296b2743b06e87fdabf94ceb419f583d8
• MCP delta: 1,565,508 bytes; SHA-256 afa3691039e094f88fcaadfbcc22bdd720cf73d50236119d1e93e02600fff3ce
• New MCP SHA-256: 9b66ec89ab096bb921d5144903756cae021f462649c752914e0efba699b97fab

Verify each asset set against its checksum manifest before running its matching applier. Pass the exact old binary, matching delta and a new output path in a trusted directory. Appliers authenticate old, delta and new bytes, create an owner-only candidate exclusively, and never overwrite an existing file or install/restart a service. Independent reconstruction matched both full-package binaries byte-for-byte; rejection checks passed.

This independent prerelease preserves earlier releases and assets. Verify the archive's adjacent checksum before extraction and its inner manifest before installation. Checksums provide integrity; no detached signature is supplied.

DBX fork Linux CLI + MCP: precise route allowlists (2026-10-03)

DBX fork Linux CLI + MCP: precise route allowlists

Verified Linux x86_64 service binaries from the complete retained fork source at c4a26c5835621285f58d25cab674630ee34c3c0b. Package version remains 0.4.102; identify this build by its commit and SHA-256 values.

Changes

• Fix the new route-update command rejecting every persistent connection-ID allowlist. An explicitly listed target can now be previewed and updated. Excluded IDs, empty allowlists, group scopes, run-scoped sessions, forbidden tools and read-only writes remain rejected; the operation does not change stored policy (fork draft #3, upstream feature #11006)
• Retain independent bounded SSE admission, selected SSH-route import and same-ID route repair, strict stored port typing, earlier CLI/MCP and safe-import changes, normal package defaults, MQ admin and DuckDB-sidecar support (upstream draft #10841)
• Retain the upstream-only mirror guard in the exact tagged source

Contents and validation

The full archive contains only bin/dbx, bin/dbx-mcp, BUILD_INFO.json, SHA256SUMS and the original DBX Apache-2.0 license. No profiles, credentials, keys or host configuration are included. The selected-export adapter and external driver/plugin sidecars remain separate dependencies.

Built and exercised in Ubuntu 22.04.5 x86_64. Both stripped binaries require glibc symbols up to 2.34 and link libc, libm, libgcc_s and the Linux loader. The CLI changed; the rebuilt MCP binary is byte-identical to the previous prerelease.

• 72 focused source tests passed, zero failed; one pre-existing external MongoDB test ignored
• 12 workflow contract tests passed
• Final release checks passed: precise allowlist admission with unchanged policy and unrelated connections/secrets; preview/apply, strict port types, wrong-key rejection and rollback; 32 SSE streams plus 80 successful tool calls and DELETE cleanup; two stdio protocol versions with the original 28 tools including MQ; synthetic selected-export integration
• These focused checks do not constitute a full workspace pass or live production database/provider/ingress validation

Full archive SHA-256: f78681baa1d9d2a1a4938e9662e02d4e67c756463c8fa77531a3fbb9ca1955d6

Canonical source SHA-256: 7a457eefcebe650bc1132b8b9134d5c6a883f6ed9297d9036d41de55f969d677 across 6,311 files. The exact digest definition and binary hashes are recorded in BUILD_INFO.json.

Optional smaller CLI transfer

Separate BSDIFF40, Python-standard-library applier, metadata and checksum assets reproduce only this release's CLI from the preceding release's exact CLI. The complete archive is also available.

• Required base CLI SHA-256: 325003908cac7e7cf63f638d3ac3a9008d03311888eb984c885ccb01f502f97d
• Delta: 701,833 bytes; SHA-256 4868465ae7a1dc8b20b04acca707d5145dbf5735f333a7b526b600860e4985eb
• Applier SHA-256: afd70d4b55f514f55cb1f1b360c1b5eb92aec0ae29d0d1dcd25ab63d8d3f2e01
• Resulting CLI SHA-256: 4787e3806e4e1ec0d17799b60a56d035cf2ba2e5a0622beb48ffe2ffddc123ad
• Unchanged MCP SHA-256: 5ab4f780e2b2da3f4fe722f80295231296b2743b06e87fdabf94ceb419f583d8

Verify the optional assets against their checksum manifest before running the applier. Pass the exact old CLI, delta and a new output path in a trusted directory. The applier authenticates all three byte sequences and creates an owner-only candidate with exclusive creation; it never overwrites an existing file or installs/restarts a service. Independent reconstruction matched the complete archive CLI byte-for-byte, and malformed-input/existing-output rejection checks passed.

This independent prerelease preserves earlier releases and assets. Verify the adjacent archive checksum before extraction and the inner manifest before installation. Checksums provide integrity; no detached signature is supplied.

DBX fork Linux CLI + MCP: route and session fixes (2026-10-03)

DBX fork Linux CLI + MCP service update

Verified Linux x86_64 service binaries from the full retained fork source at 0b53b3f6a790302e6f033c5a32923afddd7072ff. Package version remains 0.4.102; use the commit and SHA-256 values to identify this build.

Included changes

• Independent bounded SSE admission, so 32 idle notification streams do not exhaust tool-request capacity (upstream draft #10841)
• Preview-first selected SSH-route import and same-ID route updates, preserving unrelated encrypted fields and rejecting malformed stored port types (fork draft #3, upstream tracking #11006)
• Previously integrated CLI/MCP and safe-import changes retained; normal package defaults, MQ admin and DuckDB-sidecar support enabled
• Existing upstream-only mirror-publication guard retained in the tagged source

Contents and verification

The archive contains bin/dbx, bin/dbx-mcp, BUILD_INFO.json, SHA256SUMS and the unchanged DBX Apache-2.0 license. No profiles, credentials, keys or host-specific configuration are included.

Built and exercised in Ubuntu 22.04.5 x86_64. Both stripped binaries require glibc symbols up to 2.34; their linked runtime libraries are libc, libm, libgcc_s and the Linux loader. They are headless service binaries. External driver/plugin sidecars and the selected-export adapter are separate dependencies.

• 70 focused source tests passed, 0 failed; one pre-existing live MongoDB test ignored
• 12 workflow contract tests passed
• Final release-binary checks passed: 32 SSE streams plus 80 successful tool calls and DELETE cleanup; two stdio protocol versions with the original 28-tool set including MQ; route preview/apply, strict port types, wrong-key rejection, rollback and preservation of IDs/unrelated ciphertext
• Full workspace tests and real production database/provider/ingress validation are outside these synthetic checks

Archive SHA-256: 58a31b9b88881cea6b3597fe0b74142ec59d006a7e4e088f8f1129b0814b8337

Canonical source content SHA-256: 80dfbb36d81ec51da1265d8e53cb99e8037ffc3f004aced4cddcbecc72dad4df (6,311 files; exact digest definition and binary hashes are in BUILD_INFO.json).

This is a new prerelease; existing releases and assets are unchanged. Verify the adjacent archive checksum before extraction and the inner SHA256SUMS before installation. Checksums provide integrity; this archive has no detached signature.

DBX fork: authenticated remote MCP + complete integration (2026-09-30)

DBX fork integration preview: authenticated remote MCP

HTTPS deployment correction (2026-10-01)

Use the separately attached corrected Caddyfile.example and DEPLOYMENT.md, superseding the example inside the original service archive. The bundled example's unconditional respond 404 was ordered before reverse_proxy, so it returned 404 for MCP and discovery. The corrected file uses mutually exclusive routes, plus full-duplex HTTP/1 and bounded read timeouts so early 401/408/413 responses reach incomplete-upload clients.

Deployment/test source: cad01a2d8. All existing binaries, their source identity, and the release tag remain unchanged; no rebuild is required for this proxy correction. HTTPS-DEPLOYMENT-FIX.patch preserves the earlier integration and contains only deployment documentation/configuration and the regression script.

The exact published Linux service passed 41 checks for each MCP protocol version 2025-06-18 and 2025-11-25, behind actual Caddy 2.11.4: TLS 1.2/1.3, trusted CA/hostname and rejection negatives, loopback HTTP, HTTPS OAuth resource metadata/audience/challenge, token/host/origin/body boundaries, incomplete-body 408 in about five seconds, initialize/list/call with 26 tools, principal-bound sessions, live SSE and DELETE cleanup. See HTTPS-VALIDATION.json. The included test-mcp-https.py can reproduce these checks; when using it outside a source checkout, explicitly pass --caddyfile /path/to/Caddyfile.example. Test keys/profiles are ephemeral and are not committed or included in the release.

This proves real encrypted loopback proxy traffic, not independently accessible public ingress. Public DNS/ACME, a real identity-provider login, live databases and an actual ChatGPT/dot connection remain untested. DBX listens on plaintext loopback behind the TLS proxy; no gRPC transport was added. Local verification completed; the docs/tests-only source commit skips the unrelated full binary-build workflow and is not a claim that upstream CI or merge requirements passed.

Release source/tag: 2f8f792fee68e2d4bb2cf7dafb7e6eca40a58419. Tested binary source: 297c2c75875488c70643e2a9dcaccacbcfd1d199. The release commit changes only .github/workflows/sync-mirrors.yml to restrict upstream mirror publishing to the upstream repository; runtime source is unchanged. Both retain the complete prior user integration through 123c08e16730327a98f2bf4536ed8097837a8ec1.

Available and verified

• Optimized Linux x86_64 CLI + MCP service: dbx-linux-x86_64-service-ubuntu22.04.tar.gz. Built on Ubuntu 22.04/glibc 2.35; highest referenced glibc symbol is 2.34. Ubuntu 22.04 or newer is the recommended baseline. This archive is a service bundle, not a Desktop installer.
• Full-feature Linux x86_64 Desktop: dbx-linux-x86_64-desktop-full-ubuntu22.04.tar.gz. Standard Desktop features include OS keyring, DynamoDB, MQ administration, encrypted SQLite, system fonts and DuckDB-sidecar support. Built on Ubuntu 22.04; requires GTK3/WebKitGTK 4.1 and a graphical/session environment. Compilation, source, ELF architecture and checksums are verified; interactive GUI behavior has not been tested. Optional sidecars remain separate.
• Full-feature Windows x86_64 Desktop: dbx-windows-x86_64-desktop-full.zip. Standard Desktop defaults, including OS keyring, retained. Unsigned native executable archive; requires WebView2. Compilation, PE architecture, source and hashes verified; interactive GUI behavior not tested.
• Windows x86_64 CLI + MCP service with OS keyring: dbx-windows-x86_64-service-keyring.zip. Normal CLI/MCP defaults plus OS-keyring integration. Exact binaries passed native Windows CLI, stdio and OAuth HTTP smoke; requires Microsoft Visual C++ v14 x64 Runtime (VCRUNTIME140.dll). This is a console bundle, not a Windows Service installer.
• PostgreSQL Fault Lab Linux review plugin: io.xuedinge.pg-fault-lab-0.1.1-linux-x64.dbxp plus its artifact metadata. Built with the project's normal packager, Go backend/UI tests passed, and the downloaded native sidecar passed initialization, lifecycle, CLI authorization, MCP discovery/call, redaction and cleanup smoke tests. It is unsigned; installation or enabling unsigned plugins is a separate operator decision. No signing keys were generated.
• Exact tested runtime source: dbx-fork-source-297c2c758.tar.gz, including the All database picker, Fault Lab, connection CRUD, safe native/encrypted imports with stdin passphrase support, optional plaintext credential export, and the new authenticated HTTP mode.
• GitHub’s automatic source ZIP/tar for this tag includes the descendant publication guard; the exact diff is also attached as FORK-PUBLICATION-GUARD.patch.
• Deployment instructions, validation report, update notice and SHA256SUMS.

Linux and Windows service bundles, normal-feature Desktop executable archives, and the unsigned Linux plugin are now available. External agents/sidecars and OS runtime dependencies are not bundled.

Desktop packaging status

The earlier minimal-feature Linux Desktop candidate has been withdrawn: it omitted OS-keyring integration and DynamoDB, so it was not suitable as a drop-in replacement for a normal Desktop installation. It has now been replaced by the normal-default-feature Ubuntu 22.04 Desktop archive. The Windows normal-default-feature Desktop and OS-keyring-enabled service builds also completed successfully. The verified headless CLI/MCP bundle is unchanged and matches the previously installed Linux service feature baseline (duckdb-sidecar + sqlite-bundled, MQ administration disabled).

Remote MCP

The Linux service now supports an existing OAuth 2.1 provider with RS256/public JWKS access-token validation, exact issuer/resource audience, expiration/not-before checks, required scope, and an explicit profile-owner subject list. It publishes protected-resource discovery and 401/403 challenges. Stateful sessions are principal-bound; requests, streams, caches and lifecycle cleanup are bounded, including cancellation of disconnected operations on DELETE/expiry/reconfiguration.

Existing stdio/static bearer modes and DBX read-only, allowlist, dangerous-SQL, import and secret-redaction controls remain. Static bearer mode is not an OAuth login flow. Each configured OAuth subject shares the same owner-controlled DBX profile; this is not multi-tenant hosting.

Read MIGRATION-NOTES.md before moving a profile: JSON import does not move SQLite files, OS-keyring credentials or localhost/private network routes. No real key/data files are bundled.

Follow DEPLOYMENT.md for a dedicated owner-only data directory, external IdP/client registration, pinned public verification keys and an HTTPS reverse proxy. No public server was deployed, real IdP/ChatGPT account connected, or user database/profile included or probed. Completed POST-result replay is intentionally disabled; live SSE remains supported.

Validation

• 188 MCP unit tests, 12 stdio protocol tests, 2 MCP CRUD tests, 6 MCP import tests, 1 CLI CRUD test, and 9 CLI import tests passed
• Downloaded optimized Linux binaries matched CI hashes and passed synthetic-profile OAuth initialize/list/call, missing/wrong/expired/issuer/audience/scope/subject rejection, session/origin/body boundaries, DELETE, CLI and stdio smoke tests
• Exact published Windows service binaries passed native Windows Server 2022 CLI/stdin/OAuth initialize/list/call, all seven auth rejection cases, principal/session/origin/body boundaries and DELETE checks (28 tools with normal MQ-enabled defaults)
• A separate Windows Credential Manager fixture using the same keyring 3.6.3/windows-native backend passed create/read/delete/absence checks. Transport smoke used an isolated explicit file key; existing profiles and real keyrings were not inspected or migrated
• Independent scoped auth/HTTP review rechecked the session-cancellation, deadline and cache fixes
• No live database or real-provider login was used for the authentication tests

Builds: optimized Ubuntu 22 service, full-default Desktop builds, Fault Lab package, exact Windows service smoke, synthetic Windows keyring.

Upstream: Issue #10840, draft stacked PR #10841. Upstream CI requires maintainer approval; no merge or approval bypass was performed.

Keep the fork when updating

Install future updates manually from xue-ding-e/dbx Releases. Desktop's in-app updater and the original project installation scripts still point to upstream DBX. Desktop automatically checks and may download updates, but application installation requires a user action such as “Restart and update” or “Update all”. Accepting that upstream update can replace these custom changes; its post-restart component plan can also update the Desktop-managed MCP binary. The separately unpacked CLI/MCP service bundle has no self-updater. No new automatic-update channel or signing key was created.

Verify downloaded assets with SHA256SUMS. CLI/MCP identify as 0.4.102 and the source Desktop version is 0.6.29; the commit and fork release tag distinguish this integrated build.