Verify #458: document ALLOW_ZERO_RATE_LIMITS opt-out #992
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic!992
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "qa/458-verify-zero-rate-limit-guard-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Verification of GitLab #458 found the startup guard and unit tests already merged on
main(from !983), but operator docs did not yet documentALLOW_ZERO_RATE_LIMITS=1or the non-loopback bind rule. This MR adds that documentation todocs/operator-secrets.md,docs/indexer-invariants.md, andskills/AGENTS_INDEXER_API_LCD_SECURITY.md.Verification checklist (#458)
indexer/src/config.rslines 196–215:ConfigError::ZeroRateLimitNonLoopbackBindwhen dual-zero, non-loopback, non-prod, andALLOW_ZERO_RATE_LIMITSunsetcargo test --lib config::— 14/14 pass, includingdev_dual_zero_rate_limits_nonloopback_bind_rejected,dev_dual_zero_rate_limits_nonloopback_bind_allowed_with_optout,dev_dual_zero_rate_limits_loopback_bind_loads,prod_dual_zero_nonloopback_bind_loads_via_clampdocs/operator-secrets.mddocumentsALLOW_ZERO_RATE_LIMITS=1opt-outALLOW_ZERO_RATE_LIMITSandAPI_BINDrows; cross-linked #458 in rate-limit andRUN_MODE=prodsectionsdeploy-dex-local.shwritesAPI_BIND=127.0.0.1,RATE_LIMIT_RPS=0,RATE_LIMIT_LCD_HEAVY_RPS=10(not dual-zero);dev_dual_zero_rate_limits_still_loadsanddev_dual_zero_rate_limits_loopback_bind_loadspassTest plan
cd indexer && cargo test --lib config::(14 passed)ALLOW_ZERO_RATE_LIMITSand #458 cross-linksSecurity review — MR !992
Commit reviewed:
1c7f9b1c82cfde1f58beb4040f9b105bb51b0f07Scope: Documentation-only diff —
docs/indexer-invariants.md,docs/operator-secrets.md,skills/AGENTS_INDEXER_API_LCD_SECURITY.md(GitLab #458ALLOW_ZERO_RATE_LIMITSopt-out and non-loopback bind rule).Method: Inspected full MR diff; traced documented controls against existing implementation in
indexer/src/config.rs(bind_is_loopback,ConfigError::ZeroRateLimitNonLoopbackBind, prod rate-limit clamp at lines 196–215 and 248–282). No attacker-controlled input paths or executable code changed in this MR.Outcome:
FINDINGS: 0medium+Security review: no medium+ findings on this diff.
The MR adds operator/agent documentation for an already-merged startup guard (!983). Documented behavior matches code:
RATE_LIMIT_RPS=0+RATE_LIMIT_LCD_HEAVY_RPS=0) on a non-loopbackAPI_BINDrefuses startup unlessALLOW_ZERO_RATE_LIMITS=1.127.0.0.1,localhost,::1) are exempt.RUN_MODE=prodclamps both limits to 60/10 regardless; the #458 guard does not apply in prod.No injection, authz bypass, secret leakage, SSRF/XSS, or supply-chain changes introduced. Documenting the intentional opt-out does not expand runtime attack surface (requires operator env access).
Inline threads: none (no findings to anchor).
mentioned in commit
b1407f63d0