X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/054061685add05f30722971537e084f0589b601d..206568257a6df9effd66f292904d0e75c3c928ad:/redis.conf

diff --git a/redis.conf b/redis.conf
index 52520fe2..85220b80 100644
--- a/redis.conf
+++ b/redis.conf
@@ -114,6 +114,15 @@ stop-writes-on-bgsave-error yes
 # the dataset will likely be bigger if you have compressible values or keys.
 rdbcompression yes
 
+# Since verison 5 of RDB a CRC64 checksum is placed at the end of the file.
+# This makes the format more resistant to corruption but there is a performance
+# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
+# for maximum performances.
+#
+# RDB files created with checksum disabled have a checksum of zero that will
+# tell the loading code to skip the check.
+rdbchecksum yes
+
 # The filename where to dump the DB
 dbfilename dump.rdb
 
@@ -159,9 +168,17 @@ slave-serve-stale-data yes
 # You can configure a slave instance to accept writes or not. Writing against
 # a slave instance may be useful to store some ephemeral data (because data
 # written on a slave will be easily deleted after resync with the master) but
-# may also cause problems if clients are writing to it for an error.
+# may also cause problems if clients are writing to it because of a
+# misconfiguration.
 #
 # Since Redis 2.6 by default slaves are read-only.
+#
+# Note: read only slaves are not designed to be exposed to untrusted clients
+# on the internet. It's just a protection layer against misuse of the instance.
+# Still a read only slave exports by default all the administrative commands
+# such as CONFIG, DEBUG, and so forth. To a limited extend you can improve
+# security of read only slaves using 'rename-command' to shadow all the
+# administrative / dangerous commands.
 slave-read-only yes
 
 # Slaves send PINGs to server in a predefined interval. It's possible to change