Repository navigation
fix: harden A2A, MCP scoped keys, transport limits, auth, and logs - #198
Merged
Merged
Conversation
Address security tracking issues 20 through 27: - Issue 20: add A2A connection semaphore, header timeout, and line/byte caps - Issue 21: enforce MCP subscription quotas, deduplication, and bounded SSE queue - Issue 22: restrict route explanation to expert-scoped key allowlists - Issue 23: throttle MCP auth concurrency, use prefix lookup, and coalesce writes - Issue 24: restrict dashboard cookie authentication strictly to portraits - Issue 25: isolate Lemonade image requests from ambient proxies and redirects - Issue 26: defend against regex backtracking, symlink escape, and skill prompt bloat - Issue 27: sanitize sensitive tokens from scraping request and redirect logs - Release v2.50.24 with updated docs, manifests, checksums, and lockfile
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.
Addresses security tracking issues 20 through 27: