Bound in-memory attestation and session state

[AnthonyRonning]

Summary

• bound abandoned attestation handshakes to 4,096 ephemeral keys with a five-minute TTL and the Nitro nonce limit of 512 bytes
• bound encryption sessions to 65,536 entries with a 65-minute idle expiry; active use extends the idle deadline so streams are not interrupted
• return 429 when either capacity is exhausted, after pruning expired entries
• return the existing client re-attestation signal (400) when a session is missing or expired, including response-only GET/DELETE paths
• zeroize session keys when their final reference drops and remove session-key TRACE logging

The 65-minute value is an idle in-memory lifecycle, not JWT-coupled rotation. JWT refresh does not rotate the encryption session. Current TypeScript and Rust SDKs re-attest reactively on a 400 response; Maple currently pins the TypeScript SDK with that behavior.

Tests

• cargo test bounded_ttl_map::tests:: (6 passed)
• cargo test attestation_session_state_tests:: (2 passed)
• cargo clippy --all-targets --all-features -- -D warnings
• cargo test --all-features (221 passed, 16 database-dependent tests ignored, 0 failed)
• cargo fmt --all

All commands ran in the repository Nix development shell.

---

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 44a73047-f0fb-4f0f-be9b-3b94c94a99b4

📥 Commits

Reviewing files that changed from the base of the PR and between a3ecc93 and 25ba27e.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• Cargo.toml
• src/bounded_ttl_map.rs
• src/main.rs
• src/web/attestation_routes.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex-opensecret-attestation-state-bounds-opensecret

---

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.