update packages to rustls v0.23.46 to address many security advisories #43
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rust/backlog#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
The latest release of rustls, version 0.23.46, addresses four low-to-medium security vulnerabilities:
This is in addition to many other security fixes that have only landed in the v0.23 branch of rustls. Applications that still depend on rustls v0.22 or even v0.21 will need to be ported to newer versions of their dependencies.
Dependent applications:
rustls v0.23:
rustls v0.22:
rustls v0.21:
Bundled rustls:
Yet unclear affectedness:
These packages pull in rust-rustls-devel but don't contain a LICENSE.dependencies file so it cannot be checked directly whether it is actually linked into the built executables.
See also this mailing list post about dropping old and unsupported rustls versions.
update packages to and rebuild packages with rustls v0.23.46 to address many security advisoriesto update packages to rustls v0.23.46 to address many security advisoriesBuilds of rustls v0.23.46 are now available:
Dependent packages can either be rebuilt into these side-tags and attached to the existing updates, or built directly for the corresponding release(s) after these updates are stable.
I got impatient to ship a set of
trustfall-rustdoc-adapterupdates, so I’m taking care ofrust-cargo-semver-checksafter all. The neededfaster-hexandrustlsare stable everywhere except F45, where I’ll re-use and update https://bodhi.fedoraproject.org/updates/FEDORA-2026-ca950aef8f, tagging the needed dependencies into the side tag for long enough to do the rebuild.I’m also taking care of
rust-sccache(with the same approach in F45) as I patch it to accommodate a newtyped-pathrelease.@decathorpe wrote in #43 (comment):
This seems to… not exist?
What do you think is a reasonable strategy in situations like this for the applications that don’t have
rust-sigas a co-maintainer? Repeatedly going through the ceremony of trying to get consent to rebuild these as provenpackager is not something I’m interested in. And of course, Pagure doesn’t have good support for PR’s that only contain empty commits, so opening PR’s to rebuild isn’t a good approach. I guess just filing bugs and hoping the maintainers do the rebuilds would be the way to go, but this is pretty tedious without automation, too.@music wrote in #43 (comment):
(In the above category are
aw-server-rustandfips-providerfrom the packages that need to be rebuilt, plusawatcherfrom those that need to be ported. I’m currently rebuildingselenium-managersince it hasrust-sigas co-maintainer.)@music wrote in #43 (comment):
Indeed. But I consistently fail to spell kryptoci ... kcryptoc ... kryotpcoc ... kryoptic correctly. It's like a tongue twister for the fingers that one (or maybe that's just me).
@music wrote in #43 (comment):
I see two (well, three) options here:
I think the end result will be some combination of options 1 and 3.
@decathorpe wrote in #43 (comment):
Aha! This one has
rust-sig, so I’ll go ahead and rebuild it.@music wrote in #43 (comment):
Actually, the primary maintainer is shipping an update right now, so I’ll wait a bit to see which branches get left at an old version and therefore still need rebuilding.