-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent scrypt output with .NET 8 #493
Comments
Thanks for the report. I am able to reproduce it in small examples like this, though our scrypt tests pass as part of a full test suite run (but test vectors fail if run in isolation). The problem persists even when the library itself is compiled for net8.0. It doesn't seem to happen with debug builds. From a brief investigation it appears related to the intrinsics-based code in Salsa20Engine.SalsaCore (commenting that out lets everything work normally). Given all the above I would suspect some sort of bug in the runtime (probably the JIT), but I will look into it a bit further. |
@peterdettman do you have any update on this? |
We were also able the reproduce this issue and tried to solve it via an initial static call to the generator function inside a utility class. This seems to somewhat consolidate the output, although it is still inconsistent in automated test context. We are looking forward to any update regarding this issue. |
I ran into this issue and was able to reproduce it on a test deployment computer and not on a development machine, but it seems to have been resolved in a .net 8 runtime update somewhere between 8.0.2 and 8.0.10, I didn't go through each version to see when it was fixed
so replicated the random result, then after installing the .net 8.0.10 web hosting bundle in my instance:
|
Program.cs
:ScryptTest.csproj
:Expected Result (when
<TargetFramework>
isnet7.0
):Actual result (when
<TargetFramework>
isnet8.0
):The result of the first run is different every time, and the rest doesn't match the output of .NET 7.
The text was updated successfully, but these errors were encountered: