Skip to content

chore(deps): bump rustls-webpki to 0.103.16 - #5

Merged
OndrejDrapalik merged 1 commit into
mainfrom
chore/emudhra-trust-store-bump
Oct 23, 2026
Merged

OndrejDrapalik merged 1 commit into
mainfrom
chore/emudhra-trust-store-bump

Conversation

@ValentaTomas

Copy link
Copy Markdown
Member

Moves rustls-webpki 0.103.15 → 0.103.16 in driver/Cargo.lock, the version the eMudhra intermediate-CA disclosure lists as patched (it rejects chains through the compromised intermediates): https://emudhra.we-have-a-problem.com/. The lock was edited by hand (no cargo where this was prepared): rustls 0.23.45, the only dependent, requires ^0.103.14; 0.103.16 declares the same dependencies, features and MSRV as 0.103.15; and the checksum matches both crates.io's published value and a sha256 of the downloaded .crate. This repo has no CI, so reviewers: please run cargo build --locked (or cargo check --locked) in driver/ before approving.

0.103.15 -> 0.103.16 in driver/Cargo.lock, the version
https://emudhra.we-have-a-problem.com/ lists as patched. rustls 0.23.45,
the only dependent, requires ^0.103.14; the new release has the same
dependencies, features and MSRV, and its checksum is the one crates.io
publishes.
@cla-bot cla-bot Bot added the cla-signed label Oct 23, 2026
@cursor

cursor Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Single lockfile patch bump to a TLS chain-validation crate; run cargo build --locked or cargo check --locked in driver/ before merge since the lock was edited without cargo in this environment.

Overview
Updates driver/Cargo.lock so rustls-webpki goes from 0.103.15 to 0.103.16 (new crates.io checksum). That is the version called out as fixing validation against the eMudhra compromised intermediate-CA issue; rustls 0.23.45 stays on the same lock entry and still pulls this crate.

Reviewed by Cursor Bugbot for commit 5d4c693. Bugbot is set up for automated code reviews on this repo. Configure here.

@ValentaTomas

Copy link
Copy Markdown
Member Author

Compiled the lock edit at 5d4c693. It builds, and --locked leaves Cargo.lock alone.

Ran in rust:1.95.0-bookworm (the same toolchain templates/builder.ts installs), with protobuf-compiler clang cmake pkg-config libssl-dev added and the repo mounted read-only:

  • cargo build --locked in driver/: pass. 264 crates compiled, including rustls-webpki v0.103.16. Cargo.lock sha256 is the same before and after.
  • cargo test --locked: pass, 3/3.
  • cargo tree --locked -i rustls-webpki@0.103.16: it's the only rustls-webpki in the graph. It comes in through rustls 0.23.45, which is pulled by openshell-core, openshell-sandbox-backend and tokio-rustls/tonic.
  • The lock's checksum 4443b1b6…b281 matches crates.io's for 0.103.16 (not yanked), and cargo verified it on download.

Not checked: the build ran on linux/arm64 (Docker on Apple Silicon), not the x86_64 builder box. Cargo.lock doesn't depend on the target, so --locked resolution is the same either way. Only the native compile itself is arm64-only.

@OndrejDrapalik
OndrejDrapalik merged commit 9200f52 into main Oct 23, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants