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

Update misleading security claims #31

Closed
wants to merge 1 commit into from
Closed

Conversation

rurban
Copy link
Contributor

@rurban rurban commented Dec 4, 2016

See #28 and #29.

@Bulat-Ziganshin
Copy link

Bulat-Ziganshin commented Dec 4, 2016

Expected applications include DoS-proof hash tables and random generators.

i think that "DoS-proof" may be kept here since it doesn't mean any guarantees, but establish the expected application - when we need not a just another hash function, but one that can be used to protect from DoS attacks - unlike murmurhash3a, for example

@jan-wassenberg
Copy link
Member

Thanks for pointing to all the misleading spots. I have now completely rewritten each, so we can no longer apply this patch. Hopefully all concerns are now addressed ("DoS-proof" now gets an entire section); if not, please comment in #29.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants