Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare git-tagged versions to Release assets on GH #17

Open
hlein opened this issue Apr 23, 2024 · 1 comment
Open

Compare git-tagged versions to Release assets on GH #17

hlein opened this issue Apr 23, 2024 · 1 comment

Comments

@hlein
Copy link
Owner

hlein commented Apr 23, 2024

Compare & explore the differences between git-tagged versions (retrievable as generated archives from e.g. GitHub) and Release assets. The "Asset" tarball for a given version can differ from what was tagged for that release, for what are perceived as good reasons.

That discrepancy was what allowed xz-utils Release assets to have parts of the backdoor embedded that did not match what was in the Git repo.

So: how common is that? Can we bring some extra scrutiny to the differences?

@thesamesam
Copy link
Collaborator

For a first pass, I think we can do something like:

  • Check if github.com is in SRC_URI (in ebuilds) or whatever the packaging download URL is
  • Query github's API for assets for a tag (they're 1:1), the gh tool may be able to do this too
  • If any exist, see if there's one with an obvious name (like ${P}.tar.xz/.gz etc), or could even grab them all and look for e.g. configure
  • Compare

We would need to try extend this to at least gitlab and then also maybe figure out a solution for general dist-tarballs where we know of a repo but a self-hosted tarball too, but that last part feels like a stretch goal really (fairly uncommon nowadays).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants