You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.
Due to performance issues in the browser environment, it is not practical to use safe primes in wasm, and all tss-ecdsa schemes recommend safe primes, but I have seen some discussions that safe primes do not seriously affect security.
I think those links show there is not yet consensus amongst cryptographers regarding safe primes and ultimately we are constrained by the WASM runtime environment.
Currently, we had to use several workarounds to support threads and ideally we would like to remove threads so we can run in single-threaded environments where Worker is not available so if you do try some benchmarks I suggest running them on a single thread.
Let us know if you learn anything about the performance impact of safe primes and thanks for raising the issue!
However it's interesting to notice that create_safe_prime() calls generate_h1_h2_N_tilde() which in turn is not using the safe prime function from Paillier so I think it is worth asking Zengo about that.
Due to performance issues in the browser environment, it is not practical to use safe primes in wasm, and all tss-ecdsa schemes recommend safe primes, but I have seen some discussions that safe primes do not seriously affect security.
https://security.stackexchange.com/questions/73505/use-of-safe-prime-in-rsa-digital-signature-scheme
https://acsc.cs.utexas.edu/libpaillier/
https://crypto.stackexchange.com/questions/47729/safe-primes-in-rsa
Not sure what you guys think about this, given that wasm environments can only use schemes that are not safe primes.
The text was updated successfully, but these errors were encountered: