fix(tls): reject punctuation-only trust bundle identifiers - #161
fix(tls): reject punctuation-only trust bundle identifiers#161seonghobae wants to merge 5 commits into
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough신뢰 번들 식별자는 하나 이상의 ASCII 영숫자를 포함해야 합니다. 구두점만 포함한 식별자는 거부됩니다. 계약 테스트와 변경 로그를 이 정책에 맞게 업데이트했습니다. Changes신뢰 번들 식별자 검증
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This localized validation-contract change has no actionable merge-blocking risk identified at the current head and is merge-ready after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Buyer/security gap
Protected main accepted punctuation-only
TrustBundleIdentifiervalues such as---as meaningful TLS trust-policy labels. That admits identifiers with no human- or machine-distinguishing alphanumeric content into credential-free evidence and policy metadata.TDD lineage
This branch starts directly from protected main
0c376acf059be9ddddddfbde1d0189e4f39ef014.The test-first head added
---to the existing public policy-contract regression before changing production behavior. The smallest production remedy then required at least one ASCII alphanumeric while preserving the existing 1–128 byte bound and allowed punctuation set (.,_,:,-).Current implementation
Exact head
bd34717585546c6989d10ff6c2be3dc1232ad638:enterprise_roots:v1;CHANGELOG.md.The exact diff is limited to the identifier validator, its existing focused policy test, and one canonical changelog line.
Exact-head verification
On unchanged exact head
bd34717585546c6989d10ff6c2be3dc1232ad638against exact protected main0c376acf059be9ddddddfbde1d0189e4f39ef014:31866474943: success;94968267890: repository contracts, formatting, locked workspace/all-target checks, full tests, strict Clippy, and rustdoc success;94968267875: exact owned-production function, line, region, and branch coverage enforcement success;31866475016: success;31866474985: success;No predecessor-head, queued, skipped, synthetic, or model-only result is promoted as current proof.
Scope boundary
This changes no trust roots, credentials, certificate validation, network authority, workflow policy, persistence, or release behavior. Passing automation is not independent approval; protected integration remains subject to the live ruleset and unchanged-head review evidence.