- 21 Feb, 2019 2 commits
- 13 Feb, 2019 1 commit
-
-
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.
-
- 12 Feb, 2019 1 commit
-
-
zhaozhao.zz authored
In mostly production environment, normal user's behavior should be limited. Now in redis ACL mechanism we can do it like that: user default on +@all ~* -@dangerous nopass user admin on +@all ~* >someSeriousPassword Then the default normal user can not execute dangerous commands like FLUSHALL/KEYS. But some admin commands are in dangerous category too like PSYNC, and the configurations above will forbid replica from sync with master. Finally I think we could add a new configuration for replication, it is masteruser option, like this: masteruser admin masterauth someSeriousPassword Then replica will try AUTH admin someSeriousPassword and get privilege to execute PSYNC. If masteruser is NULL, replica would AUTH with only masterauth like before.
-
- 07 Feb, 2019 1 commit
-
-
antirez authored
-
- 05 Feb, 2019 1 commit
-
-
antirez authored
-
- 04 Feb, 2019 4 commits
- 31 Jan, 2019 1 commit
-
-
antirez authored
-
- 23 Jan, 2019 3 commits
- 22 Jan, 2019 1 commit
-
-
antirez authored
-
- 21 Jan, 2019 1 commit
-
-
antirez authored
-
- 18 Jan, 2019 1 commit
-
-
antirez authored
-
- 17 Jan, 2019 1 commit
-
-
antirez authored
-
- 16 Jan, 2019 1 commit
-
-
antirez authored
-
- 15 Jan, 2019 3 commits
-
-
antirez authored
-
antirez authored
This is needed in order to model the current behavior of authenticating the connection directly when no password is set. Now with ACLs this will be obtained by setting the default user as "nopass" user. Moreover this flag can be used in order to create other users that do not require any password but will work with "AUTH username <any-password>".
-
antirez authored
-
- 14 Jan, 2019 3 commits
- 11 Jan, 2019 1 commit
-
-
antirez authored
-
- 10 Jan, 2019 4 commits
- 09 Jan, 2019 10 commits