Ursa EOL about anoncreds-rs HOT 3 CLOSED

Would moving to openssl resolve some of the issues around anoncreds being slow in WASM?

from anoncreds-rs.

Would moving to openssl resolve some of the issues around anoncreds being slow in WASM?

No, that would need to be done in anoncreds-clsignatures as it is slow because of generating some 1024 bit safe primes for the credential definition.

The person behind libsodium has openssl working for WASM, https://github.com/jedisct1/openssl-wasm, but I am not sure about the build process of including this into rusts openssl-src/sys package so we can use it.

And possibly it is not even faster to use openssl-wasm instead of a pure rust as AFAIK the openssl version is quite faster because half of the big number implementation of openssl is done in assembly. Which would then be done with some polyfill / pure webassembly and I am not aware of any benchmarks between them.

from anoncreds-rs.

@andrewwhitehead Do see any additional work or is really almost everything covered by anoncreds-clsignatures?

I believe that should be the only (direct) dependency needed. If you're using the big number support directly then we may have to check that it's exposed.

The 'native' backend currently uses glass-pumpkin, but the prime generation is too slow to be practical (last I checked). A recent alternative might be crypto-primes but I haven't benchmarked that yet. There is also num-bigint-dig.

from anoncreds-rs.