NA-0284: add qsl-attachments capability scope abuse logging harness - #35
Merged
Merged
Conversation
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.
Goals: G1, G3, G4, G5
Impact: Adds executable qsl-attachments capability scope / abuse / logging harness coverage for wrong-resource and malformed capability attempts, deterministic duplicate/replay behavior under current reusable-within-scope semantics, unauthorized no-mutation/no-exposure behavior, bounded abuse loops, and log/error redaction.
No-regression: Preserves opaque-ciphertext service behavior, resource-scoped resume/fetch capabilities, fail-closed rejects, existing malformed JSON / retention / disk pressure harness behavior, no workflow changes, no dependency changes, and no production-readiness claim.
Tests/Vectors: Added
tests/capability_scope_abuse.rs,tests/capability_scope_logging.rs, and shared integration helpers undertests/support/mod.rs; validated with focused harness tests plus full locked test, clippy, and audit.Implementation code changed: no. The harness records current semantics and README clarifies reusable-within-resource-scope behavior.
No dependency changes in harness PR. No workflow changes. Loopback/local/tempdir tests only. Deterministic capability scope and abuse behavior is covered. Wrong-resource and malformed capability attempts fail closed. Unauthorized operations do not mutate or expose objects. Capability abuse logs do not leak capabilities, descriptors, ciphertext, or plaintext. Opaque-ciphertext boundary preserved.
qsl-protocol evidence will be recorded separately after this PR merges.