Upgrade tonic TLS stack#541
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthrough
ChangesDependency Version Bumps
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
0c2b75a to
158a395
Compare
158a395 to
5479654
Compare
Signed-off-by: Bisheng Huang <hbisheng@gmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: coocood, LykxSassinator The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
Upgrade
tonicfrom0.10to0.12while keeping TLS enabled.tonic 0.10'stlsfeature pulls in the olderrustls 0.21/rustls-webpki 0.101TLS stack, which is affected by RustSec advisories such asRUSTSEC-2026-0098,RUSTSEC-2026-0099, andRUSTSEC-2026-0104.tonic 0.12keeps the existingtlsfeature API but moves TLS totokio-rustls 0.26/rustls 0.23, which uses patchedrustls-webpkiversions. This keeps TLS support working while removing the vulnerable old TLS dependency path.Summary by CodeRabbit