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
We found another thread-safety issue with Kilic, described here. In short, it seems that if MulG1 is called concurrently, the two contexts will interact and give an incorrect results.
The following test exposes the problem: 10 threads are running concurrently, each performing a simple EC point multiplication with MulG1, and the result will be sent over a channel. The results are compared with a value calculated in a serial execution context, and they differ (see the failed CI build).
We found another thread-safety issue with Kilic, described here. In short, it seems that if
MulG1
is called concurrently, the two contexts will interact and give an incorrect results.The following test exposes the problem: 10 threads are running concurrently, each performing a simple EC point multiplication with
MulG1
, and the result will be sent over a channel. The results are compared with a value calculated in a serial execution context, and they differ (see the failed CI build).The text was updated successfully, but these errors were encountered: