github-starred/yaak
2
0
Fork 0
mirror of https://github.com/mountain-loop/yaak.git synced 2026-05-06 07:52:20 -05:00
Code Issues 56 Packages Projects Releases 100 Wiki Activity

[PR #434] [MERGED] Bump rustls-webpki from 0.103.7 to 0.103.10 #984

New Issue
Closed
opened 2026-04-20 19:54:48 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 19:54:48 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/mountain-loop/yaak/pull/434
Author: @dependabot[bot]
Created: 3/21/2026
Status: ✅ Merged
Merged: 4/23/2026
Merged by: @gschier

Base: main ← Head: dependabot/cargo/rustls-webpki-0.103.10

📝 Commits (1)

  • b69a055 Bump rustls-webpki from 0.103.7 to 0.103.10

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 Cargo.lock (+2 -2)

📄 Description

Bumps rustls-webpki from 0.103.7 to 0.103.10.

Release notes

Sourced from rustls-webpki's releases.

0.103.10

Correct selection of candidate CRLs by Distribution Point and Issuing Distribution Point. If a certificate had more than one distributionPoint, then only the first distributionPoint would be considered against each CRL's IssuingDistributionPoint distributionPoint, and then the certificate's subsequent distributionPoints would be ignored.

The impact was that correct provided CRLs would not be consulted to check revocation. With UnknownStatusPolicy::Deny (the default) this would lead to incorrect but safe Error::UnknownRevocationStatus. With UnknownStatusPolicy::Allow this would lead to inappropriate acceptance of revoked certificates.

This vulnerability is thought to be of limited impact. This is because both the certificate and CRL are signed -- an attacker would need to compromise a trusted issuing authority to trigger this bug. An attacker with such capabilities could likely bypass revocation checking through other more impactful means (such as publishing a valid, empty CRL.)

More likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.

This vulnerability is identified by GHSA-pwjx-qhcg-rvj4. Thank you to @​1seal for the report.

What's Changed

Full Changelog: https://github.com/rustls/webpki/compare/v/0.103.9...v/0.103.10

0.103.9

What's Changed

0.103.8

What's Changed

Full Changelog: https://github.com/rustls/webpki/compare/v/0.103.7...v/0.103.8

Commits
  • 348ce01 Prepare 0.103.10
  • dbde592 crl: fix authoritative_for() support for multiple URIs
  • 9c4838e avoid std::prelude imports
  • 009ef66 fix rust 1.94 ambiguous panic macro warnings
  • c41360d build(deps): bump taiki-e/cache-cargo-install-action from 2 to 3
  • e401d00 generate.py: reformat for black 2026.1.0
  • 06cedec Take semver-compatible deps
  • 6bc9931 Bump version to 0.103.9
  • 92dbfc6 Tie lifetime of valid_dns_names/valid_uri_names to struct lifetime
  • 2c46166 ci: sync cargo-check-external-types nightly
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note


Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/mountain-loop/yaak/pull/434 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 3/21/2026 **Status:** ✅ Merged **Merged:** 4/23/2026 **Merged by:** [@gschier](https://github.com/gschier) **Base:** `main` ← **Head:** `dependabot/cargo/rustls-webpki-0.103.10` --- ### 📝 Commits (1) - [`b69a055`](https://github.com/mountain-loop/yaak/commit/b69a055898df591b7429701908890baa076f9a4a) Bump rustls-webpki from 0.103.7 to 0.103.10 ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+2 -2) </details> ### 📄 Description Bumps [rustls-webpki](https://github.com/rustls/webpki) from 0.103.7 to 0.103.10. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rustls/webpki/releases">rustls-webpki's releases</a>.</em></p> <blockquote> <h2>0.103.10</h2> <p><strong>Correct selection of candidate CRLs by Distribution Point and Issuing Distribution Point</strong>. If a certificate had more than one <code>distributionPoint</code>, then only the first <code>distributionPoint</code> would be considered against each CRL's <code>IssuingDistributionPoint</code> <code>distributionPoint</code>, and then the certificate's subsequent <code>distributionPoint</code>s would be ignored.</p> <p>The impact was that correct provided CRLs would not be consulted to check revocation. With <code>UnknownStatusPolicy::Deny</code> (the default) this would lead to incorrect but safe <code>Error::UnknownRevocationStatus</code>. With <code>UnknownStatusPolicy::Allow</code> this would lead to inappropriate acceptance of revoked certificates.</p> <p>This vulnerability is thought to be of limited impact. This is because both the certificate and CRL are signed -- an attacker would need to compromise a trusted issuing authority to trigger this bug. An attacker with such capabilities could likely bypass revocation checking through other more impactful means (such as publishing a valid, empty CRL.)</p> <p>More likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.</p> <p>This vulnerability is identified by <a href="https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4">GHSA-pwjx-qhcg-rvj4</a>. Thank you to <a href="https://github.com/1seal"><code>@​1seal</code></a> for the report.</p> <h2>What's Changed</h2> <ul> <li>Freshen up rel-0.103 by <a href="https://github.com/ctz"><code>@​ctz</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/455">rustls/webpki#455</a></li> <li>Prepare 0.103.10 by <a href="https://github.com/ctz"><code>@​ctz</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/458">rustls/webpki#458</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/rustls/webpki/compare/v/0.103.9...v/0.103.10">https://github.com/rustls/webpki/compare/v/0.103.9...v/0.103.10</a></p> <h2>0.103.9</h2> <h2>What's Changed</h2> <ul> <li>[backport] ci: avoid denying warnings on nightly toolchains by <a href="https://github.com/alex"><code>@​alex</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/437">rustls/webpki#437</a></li> <li>Backport lifetime change and bump version for release by <a href="https://github.com/alex"><code>@​alex</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/436">rustls/webpki#436</a></li> </ul> <h2>0.103.8</h2> <h2>What's Changed</h2> <ul> <li>backport valid_uri_names (<a href="https://redirect.github.com/rustls/webpki/issues/404">#404</a>) to rel-0.103 by <a href="https://github.com/alex"><code>@​alex</code></a> in <a href="https://redirect.github.com/rustls/webpki/pull/408">rustls/webpki#408</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/rustls/webpki/compare/v/0.103.7...v/0.103.8">https://github.com/rustls/webpki/compare/v/0.103.7...v/0.103.8</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rustls/webpki/commit/348ce01c01cf8ce21199090c98853992c9c047a8"><code>348ce01</code></a> Prepare 0.103.10</li> <li><a href="https://github.com/rustls/webpki/commit/dbde5921164c6e3ea0928654de8cb7d5de8c2b33"><code>dbde592</code></a> crl: fix authoritative_for() support for multiple URIs</li> <li><a href="https://github.com/rustls/webpki/commit/9c4838e6129a544a0f7f5d26ac7517860a22992c"><code>9c4838e</code></a> avoid std::prelude imports</li> <li><a href="https://github.com/rustls/webpki/commit/009ef667e3bb0544808c39b64e9b6db0d626b117"><code>009ef66</code></a> fix rust 1.94 ambiguous panic macro warnings</li> <li><a href="https://github.com/rustls/webpki/commit/c41360d095f9f48e14679a078afd10c2d61716fe"><code>c41360d</code></a> build(deps): bump taiki-e/cache-cargo-install-action from 2 to 3</li> <li><a href="https://github.com/rustls/webpki/commit/e401d0083d9cf91d0209bae1db465267d7290233"><code>e401d00</code></a> generate.py: reformat for black 2026.1.0</li> <li><a href="https://github.com/rustls/webpki/commit/06cedecbf6af88cad40b2ae2cc4a474f1429ddb6"><code>06cedec</code></a> Take semver-compatible deps</li> <li><a href="https://github.com/rustls/webpki/commit/6bc9931d3b63d26cff9451ec59ac7efff73ebbc5"><code>6bc9931</code></a> Bump version to 0.103.9</li> <li><a href="https://github.com/rustls/webpki/commit/92dbfc6ee8ba6989d9960ec4e10dccf53820f771"><code>92dbfc6</code></a> Tie lifetime of valid_dns_names/valid_uri_names to struct lifetime</li> <li><a href="https://github.com/rustls/webpki/commit/2c46166a594c05afe111f75664c1bb4084f64e3e"><code>2c46166</code></a> ci: sync cargo-check-external-types nightly</li> <li>Additional commits viewable in <a href="https://github.com/rustls/webpki/compare/v/0.103.7...v/0.103.10">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rustls-webpki&package-manager=cargo&previous-version=0.103.7&new-version=0.103.10)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/mountain-loop/yaak/network/alerts). </details> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 19:54:48 -05:00
GiteaMirror changed title from [PR #434] Bump rustls-webpki from 0.103.7 to 0.103.10 to [PR #434] [MERGED] Bump rustls-webpki from 0.103.7 to 0.103.10 2026-04-26 00:19:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/yaak#984
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?