提交 9aba884b 编写于 作者: A antirez

Comments about security of slave-read-only in redis.coinf.

上级 3f7ad833
...@@ -159,9 +159,17 @@ slave-serve-stale-data yes ...@@ -159,9 +159,17 @@ slave-serve-stale-data yes
# You can configure a slave instance to accept writes or not. Writing against # 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 # 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 # 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. # 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 slave-read-only yes
# Slaves send PINGs to server in a predefined interval. It's possible to change # Slaves send PINGs to server in a predefined interval. It's possible to change
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册