Conversation
…sions, rate limiting, WS validation Co-authored-by: numbers-official <181934381+numbers-official@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix security issues in .gitignore and hardcoded details
Security hygiene: gitignore, redact hardcoded secrets, update versions, add rate limiting and WS origin validation
Feb 28, 2026
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.
Six medium-severity findings around information exposure and configuration hygiene. Changes address all actionable items.
.gitignoreWas a single entry (
.subnet-cli.pk). Added standard sensitive-file patterns:.env,*.pem,*.key,*.crt,*.log,.DS_Store,node_modules/.README — sensitive data exposure
app.asana.com/0/1202305127727547/...)nodeID, BLSpublicKey, andproofOfPossessionfrom exampleinfo.getNodeIDoutput — replaced with placeholder tokensOutdated software versions in update scripts
chains/update-validator-{mainnet,testnet}.shwere pinned to AvalancheGo v1.10.11 / subnet-evm v0.5.6. Updated to match README-documented production versions:Faucet Nginx — rate limiting on
/api//api/proxy had no access controls. Addedlimit_req_zone(10 req/min per IP, burst 5):RPC Nginx — WebSocket origin validation and timeouts
/wsproxy forwarded upgrade headers with no origin filtering and used nginx's default 60s read timeout (breaks long-lived connections). Added HTTPS-only origin allowlist viamapand explicit timeouts:Original prompt
🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.