Fix Docker Sandboxes startup and busy host-trust reconciliation - #42
Merged
Conversation
Accept Docker Sandboxes v0.38 blank relay-rule telemetry only after an authenticated pre-rule proof, exact scoped policy delta, and stable inventory fingerprint. Preserve fail-closed handling for missing, wrong, stale, blocked, or drifted evidence.
Use the dedicated read-only trust transport verifier during steady-state reconciliation so normal job-created runtime state does not trigger false quarantine. Preserve durable quarantine while a job is busy, avoid repeated registration fences, and resume exact cleanup once idle.
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
1 participant
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.
Summary
Verification
internal/poolnormal and race test suitesgo vetfor affected packagesgo test ./...passes except for three pre-existing Windows/WSL SSH-agent-forwarding diagnostic subcases