-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
[20.03] curl: update CVE patch hashes for extra digits added to index line #111206
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
Conversation
Actually, I see the newer versions of the curl file have a big comment right at the top that says
so I'll update this pull request to directly include the patches instead. |
Ok. I've updated the pull request to actually include the patch. Unfortunately it seems this still results in a rebuild of curl as, at least, the ultimate store path for a file is different if you fetch it vs you directly reference it as a file path. CCing @edolstra as this last bit seems a bit strange. I would have thought including a patch vs fetching it should not cause a rebuild as both would be the same fixed output. Fetching it vs referencing it ultimately gives two different paths, respectively
that are yet clearly the same file
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The commit message should change.
Include instead of using fetchpatch due to boostrapping requirement.
New commit message is curl: fix hash mismatch issue by directly include CVE patches. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified that the checked in patches are those behind the URLs. Thanks!
I just noticed this was for 20.03, not 20.09. I'm not sure the staging branch for 20.03 is still merged into release-20.03 regularly? |
Sorry. Sounds like I should have put in the request against release-20.03. I can do a new pull request against release-20.03 if you want? |
Nah, I just merged it into Just to make sure: You are aware that NixOS 20.03 is end of life for about five months now? So no guarantees about security fixes being backported. |
Got it. Thanks! 👍 |
Motivation for this change
The fetched CVE patches for curl changed so the hashes no longer agree.
Things done
I diffed the old and new versions. It seems github just added extra digits to the index lines. For example
so I just updated the hashes to match the new versions.
If this causes some sort of mass rebuild, perhaps a better solution would be to just add the old ones directly to nixpkgs to avoid having to changes any hashes. If you would prefer that, let me know and I will change it.
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)