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.

Sign up for GitHub

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

Jump to bottom

Update auto checksums from SHA1 to SHA256 #196

Closed
dtgm opened this issue May 21, 2016 · 2 comments
Closed

Update auto checksums from SHA1 to SHA256 #196

dtgm opened this issue May 21, 2016 · 2 comments

Comments

@dtgm
Copy link
Owner

dtgm commented May 21, 2016

Currently, checksums for the binary installers downloaded by packages are handled in 1 of 2 ways:

  1. Update scraped checksums from MD5/SHA1 to SHA256 (where available) #197 If a checksum is publicly available from a web-scrapable page, that is used. Only MD5 and SHA1 are retrieved.
  2. (this ticket) If no checksum is available, the auto-build machine will download the installer binary and calculate the SHA1 to be used in the package.

All packages without an available checksum should migrate to use SHA256.

ferventcoder/choco@2509f78
chocolatey/choco#113
@dtgm dtgm mentioned this issue May 21, 2016
Closed
@dtgm
Copy link
Owner Author

dtgm commented May 21, 2016 •
edited
Loading

Tasks to complete

  • Update checksum calc script from SHA1 to SHA256
  • Determine which packages use checksum calc script.
  • Update the associated tools\chocolateyInstall.ps1

dtgm added a commit that referenced this issue May 21, 2016
@dtgm
#196 Update checksum calc script from SHA1 to SHA256
19acad6
@dtgm dtgm closed this as completed in 4bbfc12 May 21, 2016
@dtgm
Copy link
Owner Author

dtgm commented May 21, 2016

Updated ~611 packages

dtgm added a commit that referenced this issue May 27, 2016
@dtgm
#196
7d6bb0d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dtgm