2.0.53

Adds the initial application-access implementation from PR #101: browser HTTP/HTTPS access through the Hub or an enrolled node, explicit access grants, independent app sessions, and support for applications retaining their native login. Add/Edit forms identify required fields and provide clickable, keyboard-accessible format guidance. Repository and wiki documentation are synchronized.

This is an initial implementation; further application-proxy work remains planned. Staging application exposure remains LAN/VPN-only.

Validation: main CI and the complete release workflow passed, including Sonar, source/artifact vulnerability gates and malware scanning. Publication contains 25 public assets; all 11 binary hashes and three published image digests were verified. The malware scan checked 85 files with no infections. Individually reviewed SQL-format warnings were resolved without changing code or quality gates. An intermittent test-cleanup failure passed on retry and remains tracked in #102.

The staging Hub is deployed at this exact release and verified healthy. All three enrolled agents reconnected; users, application definitions, grants and configuration were preserved. Live browser checks and CLI/agent distribution metadata checks passed. Node-agent binaries were not automatically upgraded.

Upgrade note: back up configuration and data consistently. Cookie hardening can require browser sign-in again. Hub startup ends existing app sessions and launch tickets; users reopen their applications. Hostname/TLS routing and protected control-address settings remain prerequisites for application access.

Commit: 5d3f167d9f804be3598813157f49d100b21f6efa

Exact scanned image digests:

docker.io/yiucloud/veyport@sha256:c15739d75076859ab20cca7354239d1873f14593667c240cc85ab14c5f305bd0
docker.io/yiucloud/veyport-audit-ingest@sha256:a90375cbf3492cb65afd8a61c2c180b6bda11345f04ff668e306ca55d39fa34b
docker.io/yiucloud/veyport-audit-export@sha256:4ad454aa7ab8fb1261ad3a83be348a4ad5d18a3305215cebc84d358fcf4707de

Binary hashes and scanner findings/classifications are attached. Completion of publication does not imply deployment or Enhanced qualification.

2.0.53-prototype.2

Application form guidance is deployed to staging at https://veyport.yiucloud.com for LAN/VPN review. PR #101 remains unmerged.

Required inputs now have a visible marker and legend. Clickable, keyboard-accessible help boxes explain accepted formats and examples, including lowercase short names and backend destination ranges versus user access grants. Add and Edit use the same guidance. Repository/wiki documentation is updated.

Validation: final CI, SonarQube, CodeQL, source/artifact vulnerability gates and malware scans passed. Live staging browser verification passed required markers, click/Enter/Space help, conditional node selection, Edit guidance without saving, and a normal-DNS/trusted-TLS demo launch (200 → 303 → 200). All seven application definitions, eleven grants, user/node identities and configuration were preserved; all three agents reconnected. A cold backup was retained before deployment.

Two initial CI attempts exposed existing test races: independent expected timestamp generation and closing a fake SSH session before attachment. Both tests were corrected without changing production behavior or removing assertions; final-source runs passed. The mobile form fits375px; an existing header overflow with the long QA username is separately recorded.

Commit: c1715edcdb72c1d0d0cf1f7c027ee722614dd462

Exact scanned image digests:

docker.io/yiucloud/veyport@sha256:4abe9b477fa9008262b85a5ee192e7bb302f3efb66550b7fda52b5a14ca04af2
docker.io/yiucloud/veyport-audit-ingest@sha256:fecc3520462ad46b181c7be244a9e7614e3744b599a4e3818d42fb5a7c3fd33f
docker.io/yiucloud/veyport-audit-export@sha256:08d5bddd3387fc96874b6f88e180b31f57ab0eec6b9112b1e46106e5f0cd202a

Binary hashes and scanner findings/classifications are attached. Completion of publication does not imply deployment or Enhanced qualification.

2.0.52

Veyport 2.0.52 fixes automatic Fleet Dashboard refresh after an enrolled-agent update (PR #100). Verified updates refresh the displayed agent version and update eligibility while the dialog is open and after it closes, without a page reload or manual refresh. Update a local CLI from its configured Hub using vey update.

Completed exact-source PR/main/release CI, CodeQL, Sonar, all 11 binaries, three images and their stable channels, 61 evidence files, CVE assessments and zero-infection malware checks were verified. Staging runs yiucloud/veyport:v2.0.52@sha256:79e7476517b8fbf5a99b7dbe17d3838685e3addeb9e855556c0fd85284566d86 with cold backup and retained checked rollback material, data identity, accounts/nodes/auth/config/policy preservation, public health/auth refusals, served artifacts and fresh agent reconnects verified. The published frontend was checked using isolated browser API fixtures and exact running image bytes. Both staging agents retain their owner-updated 2.0.51 versions.

Verified delivery evidence. No real-agent update, live CLI name execution, live login/session/SSH, Enhanced or MIL runtime qualification is claimed. Existing-MIL-Hub upgrade guidance is prepared; no MIL deployment was performed.

2.0.53-prototype.1

Application proxy prototype deployed to staging for LAN/VPN review. PR101 remains unmerged. Actual staging browser and revocation qualification passed with normal TLS verification. Shared LAN wildcard DNS was completed on 2026-10-15: *.apps.yiucloud.com → 10.10.1.27 (TTL 300). All four demo names passed normal DNS/trusted HTTPS checks. A fresh synthetic admin browser successfully clicked Open application and loaded the direct HTTP demo (launch 200, consume 303, app 200), without hostname overrides. Existing DNS records were preserved; no shared DNS restart was performed by Codex. Original qualification assets retain the historical DNS-pending result and are supplemented by this dated verification.

Deployment qualification and limits

Commit: c76c9dd17d3fbc39fbff4f0ae53fbe0200e699f2

Exact scanned image digests:

docker.io/yiucloud/veyport@sha256:eb107167f38060a5bd76544006d94758baa58341ae067e2bf936f7f0552e7858
docker.io/yiucloud/veyport-audit-ingest@sha256:173d2a12a7df801aa91f2b4ee25ffe5b01b368b41d9e3d1f6c956ecf8b8487db
docker.io/yiucloud/veyport-audit-export@sha256:321bdee484f66f47ddb62eda4180d1b439bbbf36ea67747e2b89eb025a29a796

Binary hashes and scanner findings/classifications are attached. Completion of publication does not imply deployment or Enhanced qualification.

2.0.51

Veyport 2.0.51 adds single-node enrolled-agent updates from the Fleet Dashboard and fixes CLI server-name resolution for non-admin users (PRs #98 and #99). Administrators can review the exact target and update one eligible Standard agent from its Agent Version action. Older agents that need preserving bootstrap continue through the documented direct-SSH CLI flow. CLI names resolve only within the caller’s visible servers, with existing operation permissions preserved. Update a local CLI from its configured Hub using vey update.

Completed exact-source PR/main/release CI, CodeQL, Sonar, all 11 binaries, three images and their stable channels, 61 evidence files, CVE assessments and zero-infection malware checks were verified. Staging runs yiucloud/veyport:v2.0.51@sha256:1a9fe0979a14377ed0b4a88a3d6375ab97e26c31a38b63bee3eab3858ac155d3 with cold backup and retained checked rollback material, data identity, accounts/nodes/auth/config/policy preservation, public health/auth refusals, served artifacts and fresh agent reconnects verified. The published frontend was checked using isolated browser API fixtures and exact running image bytes. Both staging agents remain prototype.9.

Verified delivery evidence. No real-agent update, live CLI name execution, live login/session/SSH, Enhanced or MIL runtime qualification is claimed. Existing-MIL-Hub upgrade guidance is prepared; no MIL deployment was performed.

2.0.50

Veyport 2.0.50 adds SSH command passthrough for CLI automation, preserving stdin, stdout, stderr and remote exit status:

vey --hub https://YOUR-HUB login
vey ssh-cert
vey servers list
vey ssh NODE -- 'hostname; id; uname -s'

This release also includes:

• vey update for the local CLI and vey servers update NODE for enrolled agents, including an explicit bootstrap path for legacy agents.
• A separate CLI inactivity policy: 45 minutes by default, while browser sessions remain 15 minutes. Session maximum age is 12 hours; running SSH commands have a separate execution limit.
• Agent versions on the Fleet Dashboard.
• CLI automation guidance, covering command quoting, stdin/scripts, OS identity, output, exit status, authentication and recovery.

For an existing Docker Compose Hub, finish active work and take a consistent cold backup of the existing configuration and complete data volume. Retain the previous image and backup together for rollback: database migrations run at startup. Preserve the existing volumes, environment, secrets, arguments and proxy settings, and replace only the Hub image with:

image: yiucloud/veyport:v2.0.50@sha256:a1685344d1d36b62bfbaa4404f5dd2d6084cc0961dc6c00daf2ea8a145bb9dda

Then, from the existing Compose directory (substitute the actual Hub service name if different):

docker compose pull veyport
docker compose up -d --no-build veyport
docker compose exec veyport /app/veyport --version

Verify version 2.0.50, Hub health, existing accounts/nodes and agent reconnects. Obtain CLI/agent updates from your own Hub. Legacy agents require an identity-preserving upgrade before command passthrough works; follow the CLI's bootstrap instructions rather than reenrolling the node. The SSH gateway needs its TCP access path, normally port 2222, in addition to HTTPS. Standard operation does not require the optional Enhanced audit services.

PR #96 was merged as 0c0cae56b2a83ed5b0c54530f3ed3f3747e3ee72, with a source tree identical to reviewed commit cfed4e2c8c20a5992a12606fc41d125f97272ae1. Main and release CI, CodeQL, Sonar, CVE and malware gates passed. All 11 published binaries, three images and attached scan evidence were independently verified. Malware scanning found zero infected files; remaining scanner matches are explicitly classified in the attached assessments.

The exact stable image is deployed to staging. Cold backup, database/account/node/configuration/policy preservation, health, unauthenticated access refusals, served artifacts and fresh agent reconnects passed. The published dashboard was checked with isolated browser API fixtures and its loaded bytes matched the running image. Existing staging agents remain prototype 9. Earlier prototype SSH, updater and session runtime qualifications are linked in the evidence; those specific manual runtime exercises were not rerun on stable. Enhanced lab and MIL deployment were not performed by this release.

Verified stable deployment evidence · Deployment guide · CLI reference

2.0.50-prototype.9

Fleet Dashboard now displays the version reported by each agent. Missing or blank versions display Not reported; existing cloudflared agent prototype.6 and bastion agent 0.1.0 remain installed.

Source: b50d4a4b2939559e5df83493da275ec3dab20cb3. The exact published staging Hub image is yiucloud/veyport:prototype-ssh-passthrough.9@sha256:4923342f924e8eff2ee520161e77d26c3bf9c9d05849b03f41b3cac9c4775bba. Fresh CI, CodeQL, ordered independent code/security reviews, Sonar quality gates, all 11 binary checks, all three public image digest checks, CVE assessments and zero-infection malware checks passed. Staging cold backup, SQLite/users/nodes/policy preservation, health, public authentication refusals, served artifacts and fresh agent reconnects passed.

Local production and published staging frontends were rendered with isolated browser-only API fixtures. Reported, legacy, absent, long and escaped version values, admin/viewer views and narrow table layout were checked. Observed staging browser asset bytes match the exact running published image. These renders qualify the display only; prototype.8 session runtime evidence remains historical. VM125 stays on Hub prototype.8; canonical agent/CLI6 and the Enhanced prototype.2 lab remain unchanged. Main merge and full stable release remain held, and PR96 remains draft.

Verified deployment evidence.

2.0.50-prototype.8

CLI sessions now default to 45 minutes of inactivity, independently of the browser’s unchanged 15-minute default. Successful authenticated CLI activity resets the idle deadline. The 12-hour absolute limit and explicit revocation remain enforced. Administrators can adjust the separate CLI setting in account policy.

This Hub change works with the existing prototype.6 CLI; no CLI or agent reinstall is required. Login inactivity does not cancel an already-running SSH command. Execution runtime limits remain separate and unchanged.

Prototype.8 is deployed to staging at the exact published image digest. Backup, database integrity, public health/authentication, served artifacts and both enrolled-node reconnects were verified. Main merge and stable release remain held for owner review.

Validation: independent code review followed by security review passed, as did PR CI, CodeQL, and the release pipeline, including SonarCloud, CVE and malware gates. All 11 published binaries and three images matched scanned artifacts. Three existing test timing/order races exposed during CI were corrected without changing production behavior or removing assertions.

The published Hub was tested with actual CLI6 and fresh synthetic MFA sessions: CLI activity at 20 minutes succeeded and reset the 45-minute deadline; CLI at 46 minutes and web at 20 minutes were refused; web activity at 14 minutes succeeded. Absolute expiry and revocation remained enforced for both session kinds. These boundary tests used guarded timestamps on new synthetic sessions, not a 45-minute wall-clock wait. All test sessions were removed, with preexisting sessions, configuration and enrolled identities preserved.

Deployment qualification and its checksum include exact source, scans, runtime results and the superseded CI attempts. Prototype.7 SSH qualification remains historical; updater, Enhanced auditing and non-amd64 runtime tests were not repeated for this policy change.

2.0.50-prototype.7

This prototype fixes SSH commands that were rejected before launch when an enrolled agent's clock was slightly ahead of the Hub, and could then return without the Veyport error or SSH exit status. Execution preparation now accepts at most five seconds of positive clock skew while enforcing a separate Hub lifetime of at most 60 seconds. Already expired preparations are rejected without an expiry grace period. Node/connection ownership, exact execution bindings, one-use attachment tickets, authorization and replay protections remain enforced.

For responsive SSH clients, Standard execution failures and Enhanced failures after complete input collection now return a visible Veyport diagnostic and nonzero SSH status even when stdin remains open. Cancellation remains immediate. A two-second watchdog bounds finalization once finishExec begins; normal successful output draining precedes that boundary and retains the existing consumer timeout. A stalled finalizer closes the SSH transport, which can also end other channels on that connection. An uncertain execution outcome remains uncertain and is not automatically retried.

The correction is in the Hub. The published Linux amd64 runtime qualification used actual prototype.6 agent and CLI binaries on a different machine from the published prototype.7 Hub. Ten exact stdout/stderr/exit-23 trials, 512 KiB of binary stdin, visible transport failure with stdin held open, and successful execution after reconnect passed. The observed failure response took 0.047 seconds across agent shutdown and transport detection; this is not a measurement of the two-second finalizer deadline. The synthetic process, node and temporary source-specific firewall rule were removed, and all seven canonical fixture identity/configuration files plus its agent binary/service were preserved. The prior published Hub6 separate-machine observation completed without reproducing an execution failure. Natural clock timestamp brackets were recorded without changing host clocks; they do not independently prove a clock-skew cause. Deterministic clock-boundary regressions cover that cause.

The disposable lab deployment helper hit its 60-second client timeout while stopping the prior Hub service, which permits a 90-second stop. The remote shell continued installing the published Hub. Exact Hub identity, the preserved canonical agent/CLI and seven identity files, backup checksum and SQLite check were verified by readback; the owned temporary archive was removed. This was a recovered lab-helper timeout, with staging unchanged during that attempt.

Source a6abe8120084ef5d19edebf28e157ff2628f1526 passed independent code review followed by security review, PR CI, CodeQL and prototype delivery. Exact public binaries/images and scanned evidence matched. CVE gates passed; malware found zero infected files among 85 scanned. Full SSH gateway race tests and focused gRPC regressions passed on the prior production-identical freeze. The first prototype.7 CI attempt exposed an existing interactive test-order race: the test removed a session before attachment completed. The test now waits for its existing attached-session lifecycle helper; ten race-detector iterations passed on the final committed test bytes and fresh exact-source CI passed. The superseded attempts were cancelled before publication. One local full unsharded gRPC run timed out at 120 seconds in an unrelated SQLite fixture; the exact test passed separately, and the required CI suites completed successfully.

Prototype 2.0.50-prototype.7 is deployed to staging with the exact published Hub digest, a cold backup and a clean SQLite check. Three users and two nodes were preserved; both agents reconnected. Public health/authentication and served artifact checks passed. This delivery preserves the owner CLI and cloudflared agent at prototype.6; the existing bastion agent remains 0.1.0. The separate Enhanced lab remains qualified on prototype.2. Prototype.6 updater qualification is historical evidence; updater and Enhanced runtime qualification were not rerun for prototype.7. Other supported platforms were cross-built and scanned. Main merge and the stable release remain held for owner review.

Deployment qualification and its checksum are attached to the release.

2.0.50-prototype.6

This prototype adds a safe preserving upgrade path for the enrolled legacy 0.1.0 agent whose version and revision linker stamps are absent. The reviewed original version and SHA-256 must be supplied together; the helper checks the installed bytes and the Hub binds the assertion to the authenticated actor, session, node, fresh connection and one-use ticket. The target must be newer. The flow preserves the existing node identity and configuration and never re-enrolls the node.

For an unstamped original, first coordinate an idle window and verify it over direct SSH. Establish the original version from trusted deployment records, then obtain its digest with sudo sha256sum /usr/local/bin/veyport-agent. Do not guess a version from an arbitrary unstamped binary. Start the operation with both flags:

vey servers update <node> --bootstrap-idle-confirmed \
  --bootstrap-original-version 0.1.0 \
  --bootstrap-original-sha256 <exact-lowercase-sha256>

Run the exact one-use direct-SSH helper command printed by the CLI. Creating the operation or printing the command does not mean installation succeeded. Inspect its operation until the Hub reports succeeded, then verify the node with vey ssh <node> -- 'hostname; id; uname -s'. Ordinary stamped-agent bootstrap keeps its existing idle-confirmation path; native updates remain unchanged.

The prototype retains the full SSH passthrough and optional Enhanced audit feature scope, the isolated self-hosted audit lab, and built-in CLI/agent updates. The existing login-hint correction uses vey --hub <hub-url> login. The separate Enhanced lab remains qualified on prototype.2; this release does not claim prototype.6 lab qualification, CMMC/FedRAMP certification, or production HA. Main merge and the stable release remain held for owner review.

The published prototype passed code review, security review, required CI, CodeQL and delivery gates for source 63840f9e1f9a831141e9f9dea8032df83152ffe9. Container/CVE and malware scans passed; malware found zero infected files among 85 scanned. On a disposable Linux amd64 system, actual published artifacts exercised the unknown original rollback outcome, direct-SSH recovery acknowledgement, and a subsequent durable bootstrap success. Seven identity/configuration files were preserved. Native agent update and rollback, CLI self-update, and SSH stdout/stderr/exit 23 checks also passed. These notes make no prototype.6 claim about the prior prototype.5 busy-agent fixture tests.

Prototype 2.0.50-prototype.6 is deployed to staging with a cold backup. The three existing users and two nodes were preserved; both agents reconnected. Public health and authentication checks passed. Main merge and stable release remain held for owner review.

Deployment qualification and its checksum are attached with the release evidence.