1. 09 Aug, 2016 1 commit
  2. 27 Jul, 2016 1 commit
    • antirez's avatar
      Ability of slave to announce arbitrary ip/port to master. · 55385f99
      antirez authored
      This feature is useful, especially in deployments using Sentinel in
      order to setup Redis HA, where the slave is executed with NAT or port
      forwarding, so that the auto-detected port/ip addresses, as listed in
      the "INFO replication" output of the master, or as provided by the
      "ROLE" command, don't match the real addresses at which the slave is
      reachable for connections.
      55385f99
  3. 20 Jul, 2016 1 commit
  4. 15 Jul, 2016 1 commit
  5. 04 Jul, 2016 1 commit
  6. 13 Jun, 2016 3 commits
  7. 05 Jun, 2016 2 commits
  8. 22 May, 2016 1 commit
  9. 10 May, 2016 1 commit
  10. 04 May, 2016 1 commit
  11. 25 Apr, 2016 1 commit
  12. 22 Apr, 2016 1 commit
    • therealbill's avatar
      fix for #3187 · 14086a46
      therealbill authored
      I've renamed maxmemoryToString to evictPolicyToString since that is
      more accurate (and easier to mentally connect with the correct data), as
      well as updated the function to user server.maxmemory_policy rather than
      server.maxmemory. Now with a default config it is actually returning
      the correct policy rather than volatile-lru.
      14086a46
  13. 29 Jan, 2016 2 commits
  14. 25 Jan, 2016 1 commit
  15. 07 Jan, 2016 1 commit
    • antirez's avatar
      New security feature: Redis protected mode. · edd4d555
      antirez authored
      An exposed Redis instance on the internet can be cause of serious
      issues. Since Redis, by default, binds to all the interfaces, it is easy
      to forget an instance without any protection layer, for error.
      
      Protected mode try to address this feature in a soft way, providing a
      layer of protection, but giving clues to Redis users about why the
      server is not accepting connections.
      
      When protected mode is enabeld (the default), and if there are no
      minumum hints about the fact the server is properly configured (no
      "bind" directive is used in order to restrict the server to certain
      interfaces, nor a password is set), clients connecting from external
      intefaces are refused with an error explaining what to do in order to
      fix the issue.
      
      Clients connecting from the IPv4 and IPv6 lookback interfaces are still
      accepted normally, similarly Unix domain socket connections are not
      restricted in any way.
      edd4d555
  16. 05 Oct, 2015 1 commit
  17. 28 Jul, 2015 1 commit
  18. 27 Jul, 2015 2 commits
  19. 26 Jul, 2015 6 commits
  20. 16 Jul, 2015 1 commit
  21. 12 Mar, 2015 2 commits
  22. 11 Mar, 2015 3 commits
  23. 10 Mar, 2015 2 commits
  24. 08 Mar, 2015 1 commit
  25. 12 Feb, 2015 1 commit
  26. 04 Feb, 2015 1 commit