cpython
webappsec-subresource-integrity
Our great sponsors
| cpython | webappsec-subresource-integrity | |
|---|---|---|
| 1 | 5 | |
| 2 | 69 | |
| - | - | |
| 0.0 | 0.0 | |
| 9 months ago | 12 months ago | |
| Python | HTML | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cpython
webappsec-subresource-integrity
-
JavaScript import maps are now supported cross-browser
Seeing this, it reminded me of an interesting topic: caching at browser-level the external libraries used for big performance improvements: https://github.com/w3c/webappsec-subresource-integrity/issue...
-
📦 Everything you need to know: package managers
All package managers implement strict specifications on this approach to integrity. For example, npm respects the W3C's "Subresource Integrity or SRI" specification, which describes the mechanisms to be implemented to reduce the risk of malicious code injection. You can jump directly here to the specification document if you want to dig deeper.
-
Python 3.11 in the Web Browser
One proposed solution is checksums on CDN provided javascript:
-
How Cloudflare verifies the code WhatsApp Web serves to users
It's great to hear that you want this added to browsers themselves, and you're right that browsers are more likely to implement such changes if you can show that users are deliberately installing an extension to add the missing functionality.
There has been some discussion at the W3C about extending the SRI spec in this direction[0], but it seems they are reluctant to do that unless "multiple browser vendors" choose to implement something like this.[1] Hopefully the existence and adoption of this browser extension helps to solve that bootstrapping / Catch-22 problem.
As for usability, would it be sufficient to just adopt a TOFU model, where the browser pins the first key it sees for a domain? To prevent the risk of permanently bricking a site (if the key gets lost, or the host gets temporarily compromised) you could politely warn the user that the key has changed, or just show a different colour icon representing that the code is correctly signed with an unknown key.
[0] https://github.com/w3c/webappsec/issues/449
[1] https://github.com/w3c/webappsec-subresource-integrity/issue...
-
“Outlook just asked me if I want to upgrade to bigger ads?”
Including the hash is exactly what subresource integrity does (even in a CDN context, conveniently enough), but so far people haven’t figured out a sufficiently non-leaky design to use it for caching[1,2].
[1] https://github.com/w3c/webappsec-subresource-integrity/issue...
[2] https://hillbrad.github.io/sri-addressable-caching/sri-addre...
What are some alternatives?
wasmtime - A fast and secure runtime for WebAssembly
mma - MMA - Musical MIDI Accompaniment. This is a mirror of the original author's code drops.
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
Roundcube - The Roundcube Webmail suite
pyground - Playground for running Python using WASM on data in the browser
compression-dictionary-transport
ci - NodeSecure tool enabling secured continuous integration
quickjspp
download-esm - Download ESM modules from npm and jsdelivr
lit - Lit is a simple library for building fast, lightweight web components.
vulnera - Programmatically fetch security vulnerabilities with one or many strategies (NPM Audit, Sonatype, Snyk, Node.js DB).