1. 15 Jul, 2020 1 commit
  2. 12 Mar, 2020 1 commit
  3. 24 Oct, 2019 1 commit
  4. 18 Sep, 2019 1 commit
  5. 09 Jan, 2019 1 commit
  6. 02 Nov, 2018 1 commit
  7. 22 Aug, 2018 1 commit
  8. 13 Jul, 2018 1 commit
  9. 03 Jul, 2018 1 commit
  10. 13 Feb, 2018 2 commits
  11. 20 Feb, 2017 1 commit
    • antirez's avatar
      Use SipHash hash function to mitigate HashDos attempts. · adeed29a
      antirez authored
      This change attempts to switch to an hash function which mitigates
      the effects of the HashDoS attack (denial of service attack trying
      to force data structures to worst case behavior) while at the same time
      providing Redis with an hash function that does not expect the input
      data to be word aligned, a condition no longer true now that sds.c
      strings have a varialbe length header.
      
      Note that it is possible sometimes that even using an hash function
      for which collisions cannot be generated without knowing the seed,
      special implementation details or the exposure of the seed in an
      indirect way (for example the ability to add elements to a Set and
      check the return in which Redis returns them with SMEMBERS) may
      make the attacker's life simpler in the process of trying to guess
      the correct seed, however the next step would be to switch to a
      log(N) data structure when too many items in a single bucket are
      detected: this seems like an overkill in the case of Redis.
      
      SPEED REGRESION TESTS:
      
      In order to verify that switching from MurmurHash to SipHash had
      no impact on speed, a set of benchmarks involving fast insertion
      of 5 million of keys were performed.
      
      The result shows Redis with SipHash in high pipelining conditions
      to be about 4% slower compared to using the previous hash function.
      However this could partially be related to the fact that the current
      implementation does not attempt to hash whole words at a time but
      reads single bytes, in order to have an output which is endian-netural
      and at the same time working on systems where unaligned memory accesses
      are a problem.
      
      Further X86 specific optimizations should be tested, the function
      may easily get at the same level of MurMurHash2 if a few optimizations
      are performed.
      adeed29a
  12. 19 Sep, 2016 1 commit
  13. 27 Jul, 2015 1 commit
  14. 26 Jul, 2015 2 commits
  15. 04 Mar, 2015 1 commit
    • antirez's avatar
      Fix iterator for issue #2438. · 509a6cc1
      antirez authored
      Itereator misuse due to analyzeLatencyForEvent() accessing the
      dictionary during the iteration, without the iterator being
      reclared as safe.
      509a6cc1
  16. 11 Feb, 2015 1 commit
  17. 08 Dec, 2014 1 commit
  18. 14 Nov, 2014 1 commit
  19. 12 Nov, 2014 2 commits
  20. 13 Aug, 2014 1 commit
  21. 11 Jul, 2014 1 commit
  22. 10 Jul, 2014 1 commit
  23. 09 Jul, 2014 1 commit
  24. 08 Jul, 2014 6 commits
  25. 07 Jul, 2014 3 commits
  26. 02 Jul, 2014 5 commits