You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, fetch_tar implements downloading the file, if a shasum does not exist, create one from the downloaded file. This is problematic as it would not catch a corrupt (or malicious) download and the whole system would continue to happily use it.
I've implemented a very rudimentary mechanism in fetch_blob that will read an arbitrary file passed to the script and use that as a check file for sha256sum. This works, but is really clunky. Ideally would want to streamline all of the hashing in to a separate process that each fetch_ mechanism could call so its not built in to the fetch_ script itself.
The text was updated successfully, but these errors were encountered:
Currently,
fetch_tar
implements downloading the file, if a shasum does not exist, create one from the downloaded file. This is problematic as it would not catch a corrupt (or malicious) download and the whole system would continue to happily use it.I've implemented a very rudimentary mechanism in
fetch_blob
that will read an arbitrary file passed to the script and use that as a check file forsha256sum
. This works, but is really clunky. Ideally would want to streamline all of the hashing in to a separate process that eachfetch_
mechanism could call so its not built in to thefetch_
script itself.The text was updated successfully, but these errors were encountered: