Skip to content
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

Closed
rurban opened this issue Apr 1, 2021 · 6 comments · Fixed by #9945
Closed

wyhash needs some kind of initial seed filtering #9553

rurban opened this issue Apr 1, 2021 · 6 comments · Fixed by #9945
Assignees
Labels
Bug This tag is applied to issues which reports bugs.

Comments

@rurban
Copy link

rurban commented Apr 1, 2021

ManDeJan/zig-wyhash#2 applies to you also.
you already updated to wyhash final 3, good, so you can use those numbers.

@rurban rurban added the Bug This tag is applied to issues which reports bugs. label Apr 1, 2021
@JalonSolov
Copy link
Contributor

@ka-weihe ^^

@ka-weihe
Copy link
Member

ka-weihe commented Apr 1, 2021

Thanks @rurban, I will do this.

@ka-weihe ka-weihe self-assigned this Apr 1, 2021
@ka-weihe
Copy link
Member

I'm closing this issue, because the wyhash_seed_init function got removed from the wyhash repo. I suppose this is because this is not needed in the newest version of wyhash? Can you confirm this @rurban or @dumblob ? Please open this issue again, if this is still a problem.

Update to newest wyhash: #9945

@rurban
Copy link
Author

rurban commented May 1, 2021

Tested the latest wyhash, which is now salted with the timestamp, but the known bad seeds are still there. Still testing though...

@dumblob
Copy link
Contributor

dumblob commented Nov 2, 2022

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 .

@rurban
Copy link
Author

rurban commented Nov 2, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This tag is applied to issues which reports bugs.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants