fix: Fix wasm32-unknown-unknown

current c2pa-rs main branch: x509-certificate v0.21.0 -> ring 0.16.20 This version of ring does not support WASI. x509-certificate v0.22.0 -> ring 0.17.5 This version of ring supports WASI and wasm32-unknown-unknown, but this version of x509-certificate added the use of ring::rand::SystemRandom to signing.rs. This works with WASI, but not wasm32-unknown-unknown. The solution was to add ring directly as a dependency with the feature wasm32_unknown_unknown_js.
contentauth · Jan 29, 2025 · 571e601 · 571e601
1 parent 09abb30
commit 571e601
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/internal/crypto/Cargo.toml b/internal/crypto/Cargo.toml
@@ -120,6 +120,7 @@ web-sys = { version = "0.3.58", features = [
 [target.'cfg(all(target_arch = "wasm32", not(target_os = "wasi")))'.dependencies]
 getrandom = { version = "0.2.7", features = ["js"] }
 js-sys = "0.3.58"
+ring = { version = "0.17", features = ["wasm32_unknown_unknown_js"]}
 
 [dev-dependencies]
 const-oid = "0.9.6"