-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subresource Integrity Hash Mismatch #6
Comments
I should note that's firefox. Chrome says: " Subresource Integrity: The resource 'https://cdn.jsdelivr.net/npm/[email protected]/dist/mermaid.min.js' has an integrity attribute, but the resource requires the request to be CORS enabled to check the integrity, and it is not. The resource has been blocked because the integrity cannot be enforced." This is self-hosted silverbullet. |
Are you on the latest version of Silverbullet? The fix for this issue was only merged about a week ago. It still doesn't work for me, but afair it's a different issue after the upgrade. |
First thing I tried was upgrading both Silverbullet and Deno M1MacBook:SilverBulletNotes mgaudet$ silverbullet upgrade |
$ silverbullet upgrade
Now going to attempt an upgrade...
So, that's done. Now let's see if this actually did anything...
Nope. I hate to tell you this, but it looks like we're still running 0.10.1. This was a bit of a futile exercise. Let's try again soon some time. Also run updating the plugs. In Firefox I see on console:
Can |
for newbies-not-developer who use self-hosted silverbullet with this plug, you can use this
Problem might be connected to this |
That |
(this may end up being fixed by a newer silverbullet release while spelunking through the code there) |
Hey,
Giving this a shot, but getting SRI hash mismatches in my console:
GET
https://cdn.jsdelivr.net/npm/[email protected]/dist/mermaid.min.js
[HTTP/1.1 503 0ms]
11:32:00.832 None of the “sha256” hashes in the integrity attribute match the content of the subresource. The computed hash is “oXlHg6q3LSBdxTKxFw0b5j69zogWtXwhrLRRwV2rlpo=”.
The text was updated successfully, but these errors were encountered: