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

Security of adding support for 5.6.0 and 5.6.1 to the workflow? #12

Closed
robrwo opened this issue Apr 8, 2024 · 3 comments
Closed

Security of adding support for 5.6.0 and 5.6.1 to the workflow? #12

robrwo opened this issue Apr 8, 2024 · 3 comments

Comments

@robrwo
Copy link

robrwo commented Apr 8, 2024

The Changes for 2.211 say:

  • Add xz 5.6.1 to workflow
    Sat Mar 9 14:56:51 2024 +0000
    953082d
    ...
  • Add xz 5.6.0 to workflow
    Sat Feb 24 10:37:19 2024 +0000
    bb252c8

But those versions are associated with the backdoor CVE-2024-3094

So do you want those versions in the workflow?

@pmqs
Copy link
Owner

pmqs commented Apr 8, 2024

Thanks @robrwo, already aware of the upstream issue and I do intend to remove those versions from the workflow. For now it isn't an issue because that workflow is broken while the upstream xz repo is disabled.

@pmqs
Copy link
Owner

pmqs commented Apr 8, 2024

My reading of the issue is the problem is only associated with the release artefacts. My workflow don't use those - it clones the xz repo & builds from source.

Regardless, prudent to remove them from the workflow regardless.

pmqs added a commit that referenced this issue Apr 8, 2024
@pmqs
Copy link
Owner

pmqs commented Apr 8, 2024

workflow updated in #12

@pmqs pmqs closed this as completed Apr 8, 2024
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