When private organizations are regulating the speech of the population? It's a necessary slope.
Because doing it without centralized government control is bad. But regulation of speech can be good. Take a look at https://www.globaltimes.cn/content/1189120.shtml for an interesting discussion.
for all hashes. lot of those top ones are not crypto hashes.
> The ecrypt result is completely irrelevant when this can not be in any way be considered cryptographically secure
Break it first, then you can say that. otherwise, what would you know?
not sure if it's because English is not your first language or just had a grumpy day or something else, this came across veeery negative. Be positive in your comments on work.
if you want to be critical doing so with positivity gives it more credibility because it shows you're able to see both sides. leading people to assume you're more likely making a balanced rather than a biased assessment, whether or not that's true.
> it is not designed for cryptography even if you extended the output to 256 bit.
You don't know that.
> This is similar to the issues
Can you break either of these?
> Making fast non-cryptographic hash functions is a fun challenge
Fun challenge? I checked out your portfolio and I didn't see any.
> I appreciate the projects
I didn't see your star. It seems more like you're jealous. And trying to make yourself feel better how about your imposter syndrome, by saying someone's work is not all that under the disguise of a public service.
For a "smart guy" that's a little easy don't you think?
So how about this, I've got a fun challenge for you. Have a shot at breaking either of these, because if you can't, you can't really claim it's insecure, can you?
Some reasons for that are: different hashes for s and s\0 (without explicitly using length) to make it harder to create collisions, related to as you say better distribution/avalanche for short strings, also design-wise I like the asymmetry that strings not perfectly divisible by 8 will be treated a little differently. I just think that makes it better overall.
BTW, not sure exactly what you mean by cross-half mixing, but I'm assuming it means mixing both halves of the 128 bit state with each other. There is that, on 3 lines 91[0], 100 and 108.
The 128 bit mix, stirs two adjacent blocks of 64 bits. Those 3 lines can mix blocks 1 & 2.
Subsequent mixes on either half then propagate that cross mix. So it does use the full 256 bit state.
> DiscoHash is included in SMHASHER [3] but its benchmark results aren't.
They are included, but understandably you missed them because it's also called BEBB4185, stated in README. Find BEBB4185 line in SMHASHER Readme.
Good question on the memory bandwidth. From memory it was a multicore system, so I think that has a higher memory bandwidth than a single core. Thanks for the STREAM thing!
It uses division and floating point!
You're welcome to try your hand at cryptanalysis. I think a lot of the statical properties are measured in the SMHasher results.
Thank you, Thaddée :)