Skip to content

fix: update TLS and Tokio security patches - #3

Open
MudassarTariq wants to merge 1 commit into
mainfrom
fix/security-tls-dependencies
Open

MudassarTariq wants to merge 1 commit into
mainfrom
fix/security-tls-dependencies

Conversation

@MudassarTariq

Copy link
Copy Markdown
Member

The released lockfile contains affected rustls, rustls-webpki, webpki-roots and Tokio versions. Refresh rustls to 0.23.46, rustls-webpki to 0.103.16, webpki-roots to 1.0.11 and Tokio to 1.51.6. The roots update includes the additional eMudhra root removals released on October 23. Keep reqwest 0.12.28 and the production client implementation unchanged.

Add local TLS tests covering rejection of an untrusted certificate, successful verified TLS with an explicitly trusted test certificate, response bodies and repeated response headers. Certificate generation and the server dependency are confined to dev-dependencies. Add an opt-in live test that verifies the real API's TLS connection and HTTP 401 mapping with an intentionally invalid key; it needs no customer credential. Add Linux and Windows test/build/package CI for Rust 1.88 and stable.

Validation on macOS arm64:

  • Original baseline: 30 unit tests passed.
  • Rust 1.88.0 and stable 1.99.1: all 32 unit tests passed; credential-dependent live tests were excluded.
  • Opt-in live TLS/invalid-key test: passed against the real API, returning HTTP 401.
  • Formatting, release build and package verification passed on Rust 1.88.0.
  • Live OSV lookup of all 171 locked registry crate versions returned no advisory matches.

Applications must update their own Cargo.lock and rebuild; updating a library lockfile does not repair existing downstream locks or binaries. The README includes the update command and patched versions. Authenticated successful single/bulk live lookups were not run. Linux and Windows results are provided by the new CI checks.

References: rustls 0.23.46, webpki certificate distrust, webpki-roots 1.0.11, Tokio I/O safety.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant