1. 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
  2. 20 Jul, 2016 1 commit
  3. 13 Jun, 2016 1 commit
  4. 10 May, 2016 1 commit
  5. 19 Apr, 2016 1 commit
  6. 01 Feb, 2016 1 commit
  7. 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
  8. 03 Dec, 2015 1 commit
  9. 15 Oct, 2015 1 commit
  10. 05 Oct, 2015 1 commit
  11. 26 Apr, 2015 1 commit
  12. 23 Apr, 2015 1 commit
  13. 19 Feb, 2015 2 commits
    • antirez's avatar
      0aa5acc8
    • antirez's avatar
      Example redis.conf binds just to 127.0.0.1. · 10246642
      antirez authored
      It's hard to pick a good approach here. A few arguments:
      
      1) There are many exposed instances on the internet.
      2) Changing the default when "bind" is not given is very dangerous,
         after an upgrade the server changes a fundamental behavior.
      3) Usually Redis, when used in a proper way, will be protected *and*
         accessed often from other computers, so this new default is likely
         not what most people want.
      4) However if users end with this default, they are using the example
         redis.conf: likely they are reading what is inside, and they'll see
         the warning.
      10246642
  14. 12 Feb, 2015 1 commit
  15. 09 Jan, 2015 1 commit
    • Matt Stancliff's avatar
      Supervise redis processes only if configured · 36a3b753
      Matt Stancliff authored
      Adds configuration option 'supervised [no | upstart | systemd | auto]'
      
      Also removed 'bzero' from the previous implementation because it's 2015.
      (We could actually statically initialize those structs, but clang
      throws an invalid warning when we try, so it looks bad even though it
      isn't bad.)
      
      Fixes #2264
      36a3b753
  16. 08 Jan, 2015 1 commit
  17. 02 Jan, 2015 1 commit
    • Matt Stancliff's avatar
      Config: Add quicklist, remove old list options · 02bb515a
      Matt Stancliff authored
      This removes:
        - list-max-ziplist-entries
        - list-max-ziplist-value
      
      This adds:
        - list-max-ziplist-size
        - list-compress-depth
      
      Also updates config file with new sections and updates
      tests to use quicklist settings instead of old list settings.
      02bb515a
  18. 02 Dec, 2014 1 commit
  19. 31 Oct, 2014 1 commit
  20. 27 Oct, 2014 1 commit
  21. 24 Oct, 2014 1 commit
  22. 29 Sep, 2014 5 commits
  23. 17 Sep, 2014 1 commit
  24. 08 Sep, 2014 1 commit
  25. 07 Aug, 2014 1 commit
  26. 28 Jul, 2014 1 commit
  27. 25 Jul, 2014 1 commit
  28. 02 Jul, 2014 1 commit
  29. 16 Jun, 2014 1 commit
    • antirez's avatar
      Client types generalized. · 56d26c23
      antirez authored
      Because of output buffer limits Redis internals had this idea of type of
      clients: normal, pubsub, slave. It is possible to set different output
      buffer limits for the three kinds of clients.
      
      However all the macros and API were named after output buffer limit
      classes, while the idea of a client type is a generic one that can be
      reused.
      
      This commit does two things:
      
      1) Rename the API and defines with more general names.
      2) Change the class of clients executing the MONITOR command from "slave"
         to "normal".
      
      "2" is a good idea because you want to have very special settings for
      slaves, that are not a good idea for MONITOR clients that are instead
      normal clients even if they are conceptually slave-alike (since it is a
      push protocol).
      
      The backward-compatibility breakage resulting from "2" is considered to
      be minimal to care, since MONITOR is a debugging command, and because
      anyway this change is not going to break the format or the behavior, but
      just when a connection is closed on big output buffer issues.
      56d26c23
  30. 22 May, 2014 1 commit
  31. 23 Apr, 2014 1 commit
  32. 15 Apr, 2014 1 commit
  33. 21 Mar, 2014 1 commit
  34. 20 Mar, 2014 1 commit
  35. 31 Jan, 2014 1 commit