-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
wyhash needs some kind of initial seed filtering #9553
Comments
@ka-weihe ^^ |
Thanks @rurban, I will do this. |
I'm closing this issue, because the Update to newest wyhash: #9945 |
Tested the latest wyhash, which is now salted with the timestamp, but the known bad seeds are still there. Still testing though... |
Just about now a new version of wyhash got released and the primary motivation behind releasing a new version is a solution (as measured by @rurban's smhasher) to the bad seeds and related problems. V shall update to the newest version rather sooner than later as it relies on wyhash on quite a lot of places. See also rurban/smhasher#243 . |
Well, the bad seeds are now much more than before (2 up to ~20), but they cause only 1 more collision (instead of 0). Which is certainly not security relevant. Concerning is that some seeds collapse now to 0, which is bad. The PerlinNoiseAV failures are gone. If v4 is better than v3 with bad seed protection? I'll think about it. With bad seed protection it is, without not. |
ManDeJan/zig-wyhash#2 applies to you also.
you already updated to wyhash final 3, good, so you can use those numbers.
The text was updated successfully, but these errors were encountered: