Repository navigation
Fix xz download URL — tukaani.org 404s post-CVE-2024-3094 hosting shift - #330
Merged
dwoz merged 1 commit intoSep 30, 2026
Merged
Conversation
dwoz
force-pushed
the
dwoz/fix/xz-download-url-github-releases
branch
from
September 30, 2026 01:36
de11d2c to
b372f6e
Compare
…VE-2024-3094 After the March 2024 xz-utils supply-chain backdoor (CVE-2024-3094), the xz project moved release hosting and authoritative release metadata from Lasse Collin's tukaani.org infrastructure to the community-maintained github.com/tukaani-project/xz repository. Tarball paths under `tukaani.org/xz/` now 404 (the listing page at `https://tukaani.org/xz/` remains up but its anchor hrefs point directly at GitHub releases), which broke the Auto-Update Versions workflow when it tried to fetch xz-5.8.4: Downloading http://tukaani.org/xz/xz-5.8.4.tar.gz... HTTP Error 404: Not Found relenv.common.RelenvException: Error fetching url ... Confirmed via curl: http://tukaani.org/xz/xz-5.8.4.tar.gz -> 301 -> https https://tukaani.org/xz/xz-5.8.4.tar.gz -> 404 https://github.com/tukaani-project/xz/releases/ download/v5.8.4/xz-5.8.4.tar.gz -> 302 -> 200 This commit makes two related changes: 1. Switch every hardcoded xz download URL to the canonical GitHub-releases template `https://github.com/tukaani-project/xz/releases/download/ v{version}/xz-{version}.tar.gz`. 2. Switch xz version *discovery* off tukaani.org too. Even though `https://tukaani.org/xz/` still returns 200 today, we shouldn't rely on that host as authoritative post-CVE. `detect_xz_versions()` now queries the tukaani-project Releases API (`https://api.github.com/repos/tukaani-project/xz/releases`), which is what tukaani.org itself now links to; drafts and prereleases (e.g. `v5.7.2beta`) are filtered. The CPE identifier `cpe:2.3:a:tukaani:xz:...` in build/windows.py is a vulnerability-DB name, not a URL, and is left alone. Files touched: - relenv/python-versions.json (5.8.2, 5.8.3 URL templates) - relenv/pyversions.py (download URL for Auto-Update Versions, stored template for new releases, detect_xz_versions -> GitHub API) - relenv/build/linux.py (fallback URL when JSON lookup fails) - relenv/build/darwin.py (fallback URL when JSON lookup fails) - tests/test_pyversions_runtime.py (mock updated to GitHub API JSON, asserts endpoint + prerelease/draft filtering) Impact: `relenv versions --check-deps` now reports `XZ 5.8.3 -> 5.8.4 (update available)` correctly, and `relenv versions --update-deps` can actually fetch the tarball. No version pin is bumped by this commit — that is the downstream job of the Auto-Update Versions workflow once this fix lands.
dwoz
force-pushed
the
dwoz/fix/xz-download-url-github-releases
branch
from
September 30, 2026 01:49
b372f6e to
8ac47c1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After the March 2024 xz-utils supply-chain backdoor (CVE-2024-3094), the xz project moved release tarball hosting from Lasse Collin's tukaani.org infrastructure to the community-maintained github.com/tukaani-project/xz repository. Tarball paths under
tukaani.org/xz/now 404 (the listing page athttps://tukaani.org/xz/remains up but its anchor hrefs point directly at GitHub releases), which broke the Auto-Update Versions workflow when it tried to fetch xz-5.8.4:Confirmed via curl:
http://tukaani.org/xz/xz-5.8.4.tar.gz -> 301 -> https
https://tukaani.org/xz/xz-5.8.4.tar.gz -> 404
https://github.com/tukaani-project/xz/releases/
download/v5.8.4/xz-5.8.4.tar.gz -> 302 -> 200
Switch every hardcoded xz download URL to the canonical GitHub-releases template. Version detection (which scrapes the tukaani.org listing page) still works and is left alone. The CPE identifier
cpe:2.3:a:tukaani:xz:...in build/windows.py is a vulnerability-DB name, not a URL, and is also left alone.Files touched:
stored template for new releases)
Impact: the Auto-Update Versions workflow can now discover and pin new xz releases; existing 5.8.2/5.8.3 pins in python-versions.json also resolve again if a fresh rebuild pulls the tarball. No version bump is performed by this commit — that is the downstream job of the automated workflow once this URL fix lands.