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
Unfortunately, subresource integrity does not support user downloaded files at the of writing. Ticket: w3c/webappsec-subresource-integrity#68
And from the ticket it also doesn't seem like support for that is coming anytime soon.
Meanwhile would it be possible to do integrity check with javascript? Could the javascript look at the download stream, run it through "$sha512" [1] hashing and notify at the end of the download if the hashsum matches or mismatches?
Threat model:
Under this threat model it would make sense if something similar to subresource integrity could be used.
Unfortunately, subresource integrity does not support user downloaded files at the of writing. Ticket: w3c/webappsec-subresource-integrity#68
And from the ticket it also doesn't seem like support for that is coming anytime soon.
Meanwhile would it be possible to do integrity check with javascript? Could the javascript look at the download stream, run it through "
$sha512
" [1] hashing and notify at the end of the download if the hashsum matches or mismatches?Tails implemented a similar solution. References:
The disadvantage is, that the user has to:
Verify your download
buttonThat's non-ideal from a usability perspective.
feature request:
Could
StreamSaver.js
automate this?[1] Writing
$
sha512
because that's just a placeholder for "hashing algorithm". Shouldn't be hardcoded to be future-proof.The text was updated successfully, but these errors were encountered: