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
Hello.
I recently learned of the polyfill.io malware issue.
Currently, SRI is supported in all major browsers.
Therefore, if the integrity attribute is specified correctly, it is possible to prevent the execution of malicious scripts on the client side.
I believe that this issue is cases where scripts for which the integrity attribute is not specified are later pollutioned.
If a server error could be returned when loading a script for which the integrity attribute is not specified, developers would have no choice but to specify the attribute in the HTML.
Hello.
I recently learned of the polyfill.io malware issue.
Currently, SRI is supported in all major browsers.
Therefore, if the integrity attribute is specified correctly, it is possible to prevent the execution of malicious scripts on the client side.
I believe that this issue is cases where scripts for which the integrity attribute is not specified are later pollutioned.
If a server error could be returned when loading a script for which the integrity attribute is not specified, developers would have no choice but to specify the attribute in the HTML.
It would be ineffective if the server cannot be trusted from the start, but I think the specification can be added without much impact.
Related:
https://lists.w3.org/Archives/Public/public-webappsec/2017Jun/0000.html
The text was updated successfully, but these errors were encountered: