From ba864e09d4e24c405ab44ac273381bfdbafff3fd Mon Sep 17 00:00:00 2001 From: antirez Date: Wed, 21 Mar 2012 12:26:05 +0100 Subject: [PATCH] Comments about security of slave-read-only in redis.coinf. --- redis.conf | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/redis.conf b/redis.conf index 8396a6a4..1b79e09e 100644 --- a/redis.conf +++ b/redis.conf @@ -159,9 +159,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 -- 2.45.2