webappsec-subresource-integrity

WebAppSec Subresource Integrity (by w3c)

Webappsec-subresource-integrity Alternatives

Similar projects and alternatives to webappsec-subresource-integrity

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better webappsec-subresource-integrity alternative or higher similarity.

webappsec-subresource-integrity reviews and mentions

Posts with mentions or reviews of webappsec-subresource-integrity. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-03.
  • JavaScript import maps are now supported cross-browser
    14 projects | news.ycombinator.com | 3 May 2023
    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
    9 projects | dev.to | 2 Nov 2022
    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
    9 projects | news.ycombinator.com | 26 Mar 2022
    One proposed solution is checksums on CDN provided javascript:

    https://w3c.github.io/webappsec-subresource-integrity/

  • How Cloudflare verifies the code WhatsApp Web serves to users
    2 projects | news.ycombinator.com | 10 Mar 2022
    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?”
    3 projects | news.ycombinator.com | 18 Feb 2022
    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...

  • A note from our sponsor - InfluxDB
    www.influxdata.com | 1 Jun 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic webappsec-subresource-integrity repo stats
5
69
0.0
about 1 year ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com