Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update rust crate rustls to 0.23 [security] - autoclosed #220

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2024

This PR contains the following updates:

Package Type Update Change
rustls workspace.dependencies minor 0.22 -> 0.23

GitHub Vulnerability Alerts

GHSA-qg5g-gv98-5ffh

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner November 25, 2024 19:56
@renovate renovate bot force-pushed the renovate/crate-rustls-vulnerability branch 5 times, most recently from 71f3c37 to 1d6febf Compare November 28, 2024 16:46
@renovate renovate bot force-pushed the renovate/crate-rustls-vulnerability branch from 1d6febf to b55bb87 Compare December 16, 2024 13:24
@renovate renovate bot changed the title chore(deps): update rust crate rustls to 0.23 [security] fix(deps): update rust crate rustls to v0.23.18 [security] Dec 16, 2024
@renovate renovate bot force-pushed the renovate/crate-rustls-vulnerability branch from b55bb87 to 0dbb720 Compare December 17, 2024 20:20
@renovate renovate bot changed the title fix(deps): update rust crate rustls to v0.23.18 [security] chore(deps): update rust crate rustls to 0.23 [security] Dec 17, 2024
Copy link
Contributor Author

renovate bot commented Dec 17, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.23.18
    Updating crates.io index
error: failed to select a version for the requirement `rustls = "^0.22"`
candidate versions found which didn't match: 0.23.18
location searched: crates.io index
required by package `awc v3.5.1`
    ... which satisfies dependency `awc = "^3.4"` (locked to 3.5.1) of package `teepot v0.3.0 (/tmp/renovate/repos/github/matter-labs/teepot/crates/teepot)`

@renovate renovate bot force-pushed the renovate/crate-rustls-vulnerability branch from 0dbb720 to 0ffb310 Compare December 20, 2024 11:01
@renovate renovate bot changed the title chore(deps): update rust crate rustls to 0.23 [security] chore(deps): update rust crate rustls to 0.23 [security] - autoclosed Dec 20, 2024
@renovate renovate bot closed this Dec 20, 2024
@renovate renovate bot deleted the renovate/crate-rustls-vulnerability branch December 20, 2024 11:45
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.

0 participants