Post #2096838

@glyph @AndresFreundTec In this case the actual malicious vector was the near-binary injected code in the practical binary of the unaudited autotools vomit (always autoreconf) which was then bundled in the actual binary artifact that was the compromised tarballs. None should have ever been part of the project. As for the test files, I still think that having a hex dump with comments explaining what flaws particular parts test would be desirable in a lot of cases.