Speed up the checksum computation in the verification extension
- Back in 2015, DAVE used to rely on a native call (`nsICryptoHash`) which is not
available anymore to WebExtensions. It was so fast that we never felt
the need to measure how many seconds it took; probably less than 5.
- The WebExtension relies on the Forge library and takes 45
seconds on a Core i5 M520, around 10 times more.
Asking upstream a new API for checksum calculation sounds hard as it
would require lobbying both Mozilla and Chrome. An alternative could be
to rewrite the checksum calculation in
An alternative could be to rewrite the checksum calculation in [WebAssembly](https://developer.mozilla.org/en-US/docs/WebAssembly).
Note that WebAssembly is currently disabled in Tor Browser, until it has been properly audited: https://trac.torproject.org/projects/tor/ticket/19417.
#4 Updated by sajolida about 1 month ago
Yes, it would be good to have some rough assessment on the feasibility of this while Enrico will be working on the iteration #1 of #16128.
We'll be 3 people working on this budget, so to think iteratively, I want to see how much iteration #1 of #16128 cost to the team before deciding if we prioritize iteration #2 of 16128 or this ticket for the next iteration.