Use SHA256SUMS file for standalone python checksum validation#1655
Use SHA256SUMS file for standalone python checksum validation#1655
SHA256SUMS file for standalone python checksum validation#1655Conversation
…#1652) * Support new release content from python-build-standalone project
for more information, see https://pre-commit.ci
SHA256SUMS file for standalone python checksum validation (#1652)SHA256SUMS file for standalone python checksum validation
|
👋 I was just bit by the issue that this PR resolves. Just a comment: I don't know what would be best, to use See something like my change on my branch: 13steinj@4bb24ed (I did this quick and dirty trying to figure out what was going on, before I stumbled upon this). |
|
Hi @13steinj, I initially started my work by considering using checksum computed by Github and available as you said in the initial API call that Requires more changes and in the end, should we trust checksum provided by GitHub or the one provided by the project itself ? |
|
Yeah just bringing up as an option in case maintainers prefer it. I just want something merged and a hotfix released sooner rather than later.
Me personally, I don't know. I mean, if you trust automated checksums by the hosting platform you can argue you're more secure than the alternative. It would solve (similar, not the same) kind of issues that happened with the (relatively recent) xz supply chain attack. |
|
@thmahe @13steinj Thanks for your contributions! Personally I would prefer the solution provided by @13steinj as it's more efficient and an extra file is not required. |
|
@dukecat0 I don't want to step on any toes here, am I good to clean my branch up a bit (mainly the whole I'd also like to:
|
Yes sure, feel free to work on it! @thmahe Still thanks for your work on this and raising the issue!
Don't worry, it's not an issue. The code guarantees that the freshness of index is always within 30 days: pipx/src/pipx/standalone_python.py Lines 125 to 142 in 849d3f4 |
|
Superseded by #1662 |
Bugfix for #1652
changelog.d/(if the patch affects the end users)No entry in
changelog.d/since this patch is a bugfix.Summary of changes
Test plan
Tested by running