Repository navigation
Conversation
ThreatCrush Security Scan14 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
Open
10 tasks
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Distributed container hosting: honest live 3-node verification
The existing
c0mpute appsprotocol already supports distributed placement, primary/standby, replica snapshots, owner-signed app records, custom domains, CLI and MCP. This PR adds a read-only, operator-run acceptance script rather than claiming a deployment without seeing independent hosts.What it tests
python3 scripts/verify-distributed-app.py --app-id <20-hex> --gateway https://A --gateway https://B [--gateway https://C] --min-holders 3 --probeGET /apps/v1/apps/<app-id>from at least two distinct gateway URLs using TLS validation (HTTP only on localhost).--proberequires successful HTTP 2xx routing to the app's health endpoint via each gateway.--previous-primaryand--previous-epoch; the operator separately stops the prior primary in staging.Self-tests
python3 scripts/verify-distributed-app.py --self-testtests valid three holders, failover, false health, insufficient/duplicate holders, gateway inconsistency, signature omissions, insecure gateway URLs. GitHub Actions workflowapps-distributed-live-verifier.ymlruns Python compilation and these tests.Limits
This does not itself cryptographically validate Ed25519 signature (the c0mpute gateway must); does not prove physical operator independence; does not verify container host isolation, real data restoration, actual latency or paid hosting. These require operator-controlled 3-host staging, Docker/iptables/IPv6 isolation tests and issue #394 acceptance before launching to arbitrary tenants. PR #393 hardens unguarded network defaults.
Merge only after CI passes.