Commit Graph
3 Commits
Author SHA1 Message Date
Satoshi Qazi Muhammed d0520842dc Move wasm-crypto off the crate versions with advisories
curve25519-dalek 2/3 -> 4.1.3 (timing variability in Scalar52::sub, on
every signature), ed25519-dalek 1 -> 2, schnorrkel 0.9 -> 0.11, merlin
2 -> 3, secp256k1 0.21 -> 0.29, tiny-bip39 0.7 -> 1.0 (drops failure),
keccak 0.1.6, rand 0.8. wee_alloc is unmaintained and is no longer the
global allocator. OSV: 9 crates with advisories before, 0 after.

secp256k1 is built with lowmemory: newer libsecp256k1 embeds about 1 MB
of precomputed tables, which would have quadrupled the wasm. The
signatures are the same; recovery uses a smaller window.

getrandom 0.2 is used with a custom backend that calls one fixed
import, wbg.ext_fill_random, which the bridge fills from
@pezkuwi/x-randomvalues. The getrandom "js" backend would have needed a
dozen new hashed wasm-bindgen imports in the bridge; the wasm now has
one import instead of 18.

The recorded known answers still hold, and signatures made by either
build verify in the other.
2026-10-12 06:17:29 +04:00
Satoshi Qazi Muhammed 39675ddfbf Check every crypto export against recorded known answers
kat.txt holds 166 deterministic outputs (hashes, pbkdf2, scrypt, bip39,
sr25519 keys, hard and soft derivation, agreement, VRF outputs, ed25519
and secp256k1 keys and signatures, recovery) and 24 sr25519/VRF
signatures, all produced by the 7.5.20 crate set. A later crate set has
to reproduce the first byte for byte and verify the second.
2026-10-12 06:17:29 +04:00
Kurdistan Tech Ministry b61206c14e feat: add all @pezkuwi/wasm-crypto packages with bizinikiwi context 2026-02-01 08:01:30 +03:00