1. 07 Oct, 2019 3 commits
    • Oran Agra's avatar
      TLS: Implement support for write barrier. · 6b629480
      Oran Agra authored
      6b629480
    • Oran Agra's avatar
      diskless replication rdb transfer uses pipe, and writes to sockets form the parent process. · 5a477946
      Oran Agra authored
      misc:
      - handle SSL_has_pending by iterating though these in beforeSleep, and setting timeout of 0 to aeProcessEvents
      - fix issue with epoll signaling EPOLLHUP and EPOLLERR only to the write handlers. (needed to detect the rdb pipe was closed)
      - add key-load-delay config for testing
      - trim connShutdown which is no longer needed
      - rioFdsetWrite -> rioFdWrite - simplified since there's no longer need to write to multiple FDs
      - don't detect rdb child exited (don't call wait3) until we detect the pipe is closed
      - Cleanup bad optimization from rio.c, add another one
      5a477946
    • Yossi Gottlieb's avatar
      TLS: Connections refactoring and TLS support. · b087dd1d
      Yossi Gottlieb authored
      * Introduce a connection abstraction layer for all socket operations and
      integrate it across the code base.
      * Provide an optional TLS connections implementation based on OpenSSL.
      * Pull a newer version of hiredis with TLS support.
      * Tests, redis-cli updates for TLS support.
      b087dd1d
  2. 02 Sep, 2019 1 commit
  3. 31 Jul, 2019 1 commit
  4. 24 Jul, 2019 1 commit
  5. 23 Jul, 2019 3 commits
  6. 22 Jul, 2019 1 commit
  7. 10 Jul, 2019 1 commit
  8. 08 Jul, 2019 1 commit
    • Oran Agra's avatar
      diskless replication on slave side (don't store rdb to file), plus some other related fixes · 2de544cf
      Oran Agra authored
      The implementation of the diskless replication was currently diskless only on the master side.
      The slave side was still storing the received rdb file to the disk before loading it back in and parsing it.
      
      This commit adds two modes to load rdb directly from socket:
      1) when-empty
      2) using "swapdb"
      the third mode of using diskless slave by flushdb is risky and currently not included.
      
      other changes:
      --------------
      distinguish between aof configuration and state so that we can re-enable aof only when sync eventually
      succeeds (and not when exiting from readSyncBulkPayload after a failed attempt)
      also a CONFIG GET and INFO during rdb loading would have lied
      
      When loading rdb from the network, don't kill the server on short read (that can be a network error)
      
      Fix rdb check when performed on preamble AOF
      
      tests:
      run replication tests for diskless slave too
      make replication test a bit more aggressive
      Add test for diskless load swapdb
      2de544cf
  9. 03 Jul, 2019 1 commit
  10. 07 Jun, 2019 1 commit
  11. 06 May, 2019 9 commits
  12. 20 Mar, 2019 1 commit
  13. 18 Mar, 2019 1 commit
  14. 03 Mar, 2019 1 commit
  15. 27 Feb, 2019 1 commit
  16. 25 Feb, 2019 1 commit
  17. 21 Feb, 2019 1 commit
  18. 13 Feb, 2019 2 commits
    • zhaozhao.zz's avatar
      ACL: show categories in COMMAND reply · 14507457
      zhaozhao.zz authored
      Adding another new filed categories at the end of
      command reply, it's easy to read and distinguish
      flags and categories, also compatible with old format.
      14507457
    • antirez's avatar
      ACL: tag LASTSAVE as dangerous. · e819c2ef
      antirez authored
      That's not REALLY needed, but... right now with LASTSAVE being the only
      command tagged as "admin" but not "dangerous" what happens is that after
      rewrites the rewrite engine will produce from the rules:
      
          user default on +@all ~* -@dangerous nopass
      
      The rewrite:
      
          user default on nopass ~* +@all -@admin -@dangerous +lastsave
      
      Which is correct but will have users wondering about why LASTSAVE has
      something special.
      
      Since LASTSAVE after all also leaks information about the underlying
      server configuration, that may not be great for SAAS vendors, let's tag
      it as dangerous as well and forget about this issue :-)
      e819c2ef
  19. 12 Feb, 2019 1 commit
  20. 11 Feb, 2019 1 commit
  21. 07 Feb, 2019 1 commit
  22. 05 Feb, 2019 1 commit
  23. 04 Feb, 2019 1 commit
  24. 23 Jan, 2019 4 commits