Add Subresource Integrity hashes for FFmpeg WASM CDN resources (Issue #1703) - #1715
Add Subresource Integrity hashes for FFmpeg WASM CDN resources (Issue #1703)#1715anshul23102 wants to merge 1 commit into
Conversation
Fixes magic-peach#1703 Implements SRI (Subresource Integrity) verification for all FFmpeg WASM and JavaScript files loaded from cdn.jsdelivr.net. Prevents tampering with CDN-served resources and ensures cryptographic verification of loaded content. Changes: - Restructured SRI_HASHES to support both UMD (v0.12.10) and ESM (v0.12.6) versions - Updated fetchWithIntegrity to validate against versioned hashes - Added verification for ffmpeg-core.js, ffmpeg-core.wasm, and ffmpeg-core.worker.js - Throws error if SRI hash is missing instead of silently falling back All CDN resources now load with integrity verification enabled.
|
@anshul23102 is attempting to deploy a commit to the magic-peach1's projects Team on Vercel. A member of the Team first needs to authorize it. |
👋 Thanks for your PR, @anshul23102!Welcome to Reframe — a browser-based video editor built for everyone 🎬 What happens next
Quick checklist
Useful links
Happy coding! 🎉 |
|
Hi @magic-peach team! 👋 I've implemented the security fix for Issue #1703 (SRI hashes for CDN resources). What's Included✅ SRI verification for ffmpeg-core.js, ffmpeg-core.wasm, ffmpeg-core.worker.js For ReviewWhen reviewing, labels valuable for GSSoC 2026:
Ready for review! 🚀 Contributed as part of GSSoC 2026 |
|
Summary
Implements cryptographic verification (SRI) for all FFmpeg WASM and JavaScript files loaded from cdn.jsdelivr.net. This prevents CDN tampering attacks and ensures resource integrity.
Changes
Security Benefits
✅ Prevents CDN tampering attacks
✅ Cryptographic verification of all loaded content
✅ Compliant with security best practices for third-party resources
Fixes #1703
Testing