Repository navigation
Omit Security session traces from span reads - #1856
Merged
Merged
Conversation
A read token can open an ordinary Run's span and waterfall routes. Those routes already skip Security session files. The regression now also asks for that session and its tool call by span id, and checks the Run's other stage and ordinary session stay visible. A security token still receives the trace.
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.
Summary
An ordinary Run keeps its other stages. A Security session on that Run stays out of span, waterfall, and single-span reads unless the caller has the security scope.
The omission was already in
load_without_security_sessions. This change locks the single-span read, the ordinary Run, and the session's tool call.Seams
/api/v1/spans,/api/v1/waterfall) for a token with and without the security scope/api/v1/spans?span=<id>) of that Security session, its tool call, and the Run's ordinary sessionEvidence
Execution evidence
The product filter was not the failure. The HTML route is not a token read, so that request was removed.
After:
cargo test --test console tokens::read_scope_cannot_read_a_security_session_through_spans -- --exactUnaddressed findings
None. Standards and Spec each reported no findings. The review left no changed file unread.
Security
No unaddressed introduced findings.
Security review outcome
No unaddressed introduced findings.
Merge Danger
Door: two-way
Test-only. Reverting the commit removes the regression and leaves the span filter as it is.
Blast Radius: none
No runtime change. The new assertions cover Console span reads for an ordinary Run.
Closes #1855
Built with grok grok 1.0.70 (f50904eaee6c) [stable] · default model · default effort