Repository navigation
CyberGrid v0.8.0
CyberGrid v0.8.0 pairs static product policy, finite registration admission and explicit host remote-access gates with the matching Rust and browser SDKs. A host fixes its real Logto Native/SPA clients and canonical product; a finite-v2 deployment requires matching clients and a separate Redis prefix. Existing v0.7.0 assets remain unchanged.
The independent component versions are Rust SDK 0.3.0, JS/TypeScript SDK 0.2.0, Lab 0.4.0, Node server 0.2.0, and the first RAM-only workspace sample 0.1.0. The historical Go SDK/CLI remains 0.4.0 and does not gain finite admission, remote gates or browser bridge APIs. Use matched archives from this project release; version metadata alone is not runtime acceptance.
- Rust retains WebRTC → direct-only iroh → Quick Tunnel with inner mTLS, and adds explicit remote enable/disable, context-aware fresh-token requests, owned cancellation and finite-admission recovery. Local application services remain independent of remote access.
- The JS SDK remains a read-only console identity: it does not register Native devices, publish or acquire generic TCP access. It adds bounded directory/watch, fresh-token context, layered snapshots and gated business adapters. Unknown, changed identity/descriptor/policy, expiry and cancellation close the business gate. No business write is automatically replayed.
- Lab uses the matching Rust SDK and explicit remote controls; Android debug-test builds support the matching ADB protocol. Official platform Logto owners retain grant ownership. The separate RAM-only sample uses official in-memory owners and local/remote entry isolation; its default public build has no external Gateway/Noise adapter and reports unavailable for that path.
CyberGrid-0.8.0-source.tar.gzandcybergrid-source-manifest.jsonpreserve the complete reviewed public repository, including server/SDK relative dependencies, the desktop/Web sample, locks, public configuration example and notices. Component source packages remain available; standalone Rust archives do not contain repository Node/Redis integration prerequisites.- The browser ESM package contains exactly index, bridge, directory and endpoints modules and types, package metadata, README and licenses. No private AnyWork adapter, AGPL implementation, cloud credentials or user data is bundled.
- The required repository workflow uses actual Redis, controlled OAuth/JWK and both native/browser module integrations. These fixtures are not real Logto Cloud login, public Noise/Quick Tunnel, phone-network or 30-minute/8-hour/24-hour acceptance. Those results remain separately gated by integration-010 and must be reported for the actual final release scope.
- Mac arm64 App/CLI and Android arm64 API28+ debug-test APK/CLI remain test artifacts. Mac is not notarized. CI Android signing is ephemeral: preserve existing authorization and signing ownership before handling a signature mismatch; do not uninstall a user's authorized app to force an upgrade.
- Full source/license manifests, provider pins,
release-manifest.jsonandSHA256SUMSbind assets to the exact public snapshot commit and Actions run. Local unpublished history is not uploaded; the reviewed local freeze → exported tree → public commit mapping is retained separately.
This v0.8.0 release publishes CI-built macOS arm64 and Android arm64 debug-test installation packages from commit f2a3961. These packages are provided for testing; release publication and repository fixture CI do not declare production-client acceptance or completion of integration-010. Real dual-device Logto Cloud authorization, bidirectional Wi-Fi/4G WAN transport verification and the remaining 30-minute/8-hour/24-hour runtime acceptance are not completed by this release. Mac notarization is not provided; Android debug signing is ephemeral, so preserve existing authorization and signing ownership and do not uninstall an authorized app to bypass a signature mismatch.
Original CyberGrid code retains all rights reserved; no new SDK embedding or redistribution grant is implied. Third-party licenses and original notice bytes remain effective.