antirez 5a4133034e SipHash 2-4 -> SipHash 1-2.
For performance reasons we use a reduced rounds variant of
SipHash. This should still provide enough protection and the
effects in the hash table distribution are non existing.
If some real world attack on SipHash 1-2 will be found we can
trivially switch to something more secure. Anyway it is a
big step forward from Murmurhash, for which it is trivial to
generate *seed independent* colliding keys... The speed
penatly introduced by SipHash 2-4, around 4%, was a too big
price to pay compared to the effectiveness of the HashDoS
attack against SipHash 1-2, and considering so far in the
Redis history, no such an incident ever happened even while
using trivially to collide hash functions.
2017-02-21 17:16:35 +01:00
..
2016-04-25 16:49:57 +03:00
2016-04-25 16:49:57 +03:00
2016-06-07 16:46:00 -04:00
2016-04-04 14:13:46 +02:00
2016-04-04 08:50:58 +02:00
2016-04-04 08:50:58 +02:00
2016-10-19 10:43:40 +02:00
2015-10-01 13:02:25 +02:00
2017-02-21 17:16:35 +01:00
2017-01-12 09:59:30 +01:00
2016-07-27 11:34:25 +02:00
2016-07-27 11:34:25 +02:00
2016-06-14 14:45:28 +02:00
2015-07-27 14:37:58 +02:00
2015-07-27 14:37:58 +02:00
2017-01-30 10:09:45 +01:00
2015-07-27 14:37:58 +02:00
2014-08-08 10:05:32 +02:00
2016-12-19 08:54:46 +01:00
2017-01-13 11:34:55 +01:00
2016-10-10 01:13:20 +09:00
2017-01-27 10:49:25 +01:00
2016-04-25 16:49:57 +03:00
2015-04-27 12:07:49 +02:00
2015-04-27 12:07:49 +02:00
2017-02-21 17:16:35 +01:00
2014-07-02 16:31:22 +02:00
2016-09-12 13:19:05 +02:00
2016-05-10 06:40:05 +02:00
2016-12-06 09:30:00 +01:00
2017-02-01 17:01:41 +01:00