Hacker GitHub

← All repos

tukaani-project/xz

View on GitHub ↗ ★ 1,704 C

XZ Utils

38 mentions on Hacker News by 36 people: 6 stories, 32 comments · first 2024-03-17 · latest 2024-05-19

Mentions per year 38 mentions · busiest year 2024 (38)
20082026
  1. …seems fine to me. The maintainers are doing the latter, I’d say this is a good response. [1]: https://github.com/tukaani-project/xz/issues/121
  2. …fairness, Jia was indeed the co-maintainer of the project. He modified SECURITY.md as well[1]. [1] https://github.com/tukaani-project/xz/commit/780d2c236de0e47...
    comment by johnisgood · 2024-04-13 · in XZ backdoor story – Initial analysis
  3. Very funny. This one: https://github.com/tukaani-project/xz/commits?author=thesame... https://github.com/thesamesam Seems like he's a Gentoo contributor.
    comment by asveikau · 2024-04-13 · in XZ backdoor story – Initial analysis
  4. …code's extension hooks. This is done with what should have been a highly suspicious commit: https://github.com/tukaani-project/xz/commit/6e636819e8f0703... - this replaces "random" test files with other "random" test files. The state reson…
  5. https://github.com/tukaani-project/xz/commit/77a294d98a9d2d4... Special author: Jia Tan was a co-maintainer in 2022-2024. He and the team behind him inserted a backdoor (CVE-2024-3094) into XZ Utils 5.6.0 and 5.6.1 releases. He suddenly…
    comment by glandium · 2024-04-10 · in The xz-utils backdoor has been removed
  6. https://github.com/tukaani-project/xz/commit/780cbf29d5a88db... to update the NEWS file is equally honest: 5.6.1 (2024-03-09) IMPORTANT: This fixed bugs in the backdoor (CVE-2024-3094) (someone had forgot to run Valgrind).
    comment by syntheticcdo · 2024-04-10 · in The xz-utils backdoor has been removed
  7. This commit message is gold: https://github.com/tukaani-project/xz/commit/e93e13c8b3bec92... While the backdoor was inactive (and thus harmless) without inserting a small trigger code into the build system when the source package was…
    comment by rgovostes · 2024-04-10 · in The xz-utils backdoor has been removed
  8. The security policy was also updated: https://github.com/tukaani-project/xz/commit/780d2c236de0e47...
    comment by EveryPizza · 2024-04-09 · in The xz-utils backdoor has been removed
  9. Internet Archive to the rescue! It's still possible to download the liblzma source code from the Internet Archive's Github snapshot of the 5.4.6 stable release: https://web.archive.org/web/20240329182145/https://github.co...
    comment by mttpgn · 2024-04-05 · in FFmpeg 7.0
  10. In https://archive.softwareheritage.org/browse/revision/e446ab7... one can open the patches and then click the "Changes" sub-tab. Stuff like this looks like a perf improvement but who knows if a tricky bug is introduced that was aimed to…
    comment by goombacloud · 2024-04-02 · in Timeline of the xz open source attack
  11. Hello everybody. I am taking the initiative to gather more information regarding the possible precursors and perpetrators of the backdoor. The purpose of this commentary is focused on open source information (OSINT). I am not a judge of…
  12. Now the GitHub repo has been disabled by GitHub due to violation of GitHub's terms. https://github.com/tukaani-project/xz
    comment by marco_patino · 2024-03-31 · in Xz/liblzma: Bash-stage Obfuscation Explained
  13. Update: found a repo(thanks to @ar-jan on GitHub), https://archive.softwareheritage.org/browse/origin/directory...
    comment by AverseABFun · 2024-03-30 · in GitHub Disabled the Xz Repo
  14. Apparently there's a wayback machine for git repos and it "just coincidentally" archived this repo the day before the news broke: https://archive.softwareheritage.org/browse/origin/visits/?o...
  15. The answer is not complete. There were 2 ways to pull sources: bad - https://github.com/tukaani-project/xz/releases/download/ ... or: good - https://github.com/tukaani-project/xz/archive/refs/tags/ ... Specifically in Gentoo, there is a…
  16. You're right, but maybe because there's nothing to see : https://github.com/tukaani-project/xz
    comment by az09mugen · 2024-03-30 · in GitHub Disabled the Xz Repo
  17. Hello, Github just disabled the repo : https://github.com/tukaani-project/xz Do someone have an up to date fork to see the project history ?
  18. …> tests/files/good-large_compressed.lzma > committed upstream. They were initially added in > https://github.com/tukaani-project/xz/commit/cf44e4b7f5dfdbf...
  19. It's not a problem, never has been. Nix mirrors all source bundles it pulls from third parties and caches them. cache.nixos.org has a copy of all the sources needed to build not just current HEAD, but also past commits (although deep…
    comment by dave_universetf · 2024-03-30 · in GitHub Disabled the Xz Repo
  20. …issue pretty difficult, when GitHub has revoked everyone's access to see the affected source code. https://github.com/tukaani-project/xz vs https://github.com/JiaT75
  21. Interestingly: https://github.com/tukaani-project/xz/issues/62#issuecomment...
  22. …timezone. Below are links to the git mailbox files where you could see the timezone. From 2022: - https://github.com/tukaani-project/xz/commit/c6977e740008817... - https://github.com/tukaani-project/xz/commit/7c16e312cb2f40b... From 2024:…
  23. …is tagged `upstream/v5.6.0` despite the script itself not being present on that tag upstream: https://github.com/tukaani-project/xz/tree/v5.6.0/m4 > I'm also suggesting that there could be more than one exploit present. All of their…
  24. …binary needed to be modified for the exploit to work[1] which was later picked up by build system. https://github.com/tukaani-project/xz/commit/6e636819e8f0703...
  25. That was a review of someone else's work? https://github.com/tukaani-project/xz/pull/86
  26. Also I see this PR: https://github.com/tukaani-project/xz/pull/64
  27. …report by emailing us at [xz@tukaani.org](mailto:xz@tukaani.org), or through [Security Advisories](https://github.com/tukaani-project/xz/security/advisories/new). -While both options are available, we prefer email. In any case, please…
  28. …is "authored by" Lasse Collin in the git metadata, but the code actually came from Hans Jansen: https://github.com/tukaani-project/xz/commit/ee44863ae88e377... > Thanks to Hans Jansen for the original patch.…
  29. > "Docs: Simplify SECURITY.md." https://github.com/tukaani-project/xz/commit/af071ef7702debe... Removes instructions about details relevant to security reports. Heh, nice one.
  30. …is weirdly a simplification of the security reporting process, to not request as much detail: https://github.com/tukaani-project/xz/commit/af071ef7702debe... Not sure what to make of this.
  31. …git repo is "Simplify SECURITY.md", committed by the same Github account which added the backdoor. https://github.com/tukaani-project/xz/commit/af071ef7702debe...
  32. …ifuncs and inlining (all at the same time): https://bugzilla.redhat.com/show_bug.cgi?id=2267598 https://github.com/tukaani-project/xz/commit/82ecc538193b380...
    comment by rwmj · 2024-03-17 · in The return of the frame pointers