- 28 Feb, 2019 2 commits
- 27 Feb, 2019 3 commits
-
-
antirez authored
As documented but never implemented.
-
vattezhang authored
-
antirez authored
-
- 26 Feb, 2019 1 commit
-
-
Madelyn Olson authored
-
- 25 Feb, 2019 6 commits
- 24 Feb, 2019 1 commit
-
-
antirez authored
-
- 22 Feb, 2019 4 commits
- 21 Feb, 2019 9 commits
-
-
antirez authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
Oran Agra authored
* bigkeys used to fail on databases with module type keys * new code adds more types when it discovers them, but has no way to know element count in modules types yet * bigkeys was missing XLEN command for streams * adding --memkeys and --memkeys-samples to make use of the MEMORY USAGE command see #5167, #5175
-
- 20 Feb, 2019 1 commit
-
-
artix authored
Fix issue #5849
-
- 19 Feb, 2019 2 commits
- 18 Feb, 2019 2 commits
- 14 Feb, 2019 1 commit
-
-
antirez authored
Reltaed to discussion and PR #5840.
-
- 13 Feb, 2019 5 commits
-
-
Madelyn Olson authored
-
Madelyn Olson authored
-
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.
-
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 :-)
-
zhaozhao.zz authored
-
- 12 Feb, 2019 3 commits
-
-
antirez authored
-
antirez authored
-
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.
-