-
Notifications
You must be signed in to change notification settings - Fork 702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move auth check to the front #1475
base: unstable
Are you sure you want to change the base?
Move auth check to the front #1475
Conversation
When requirepass is enabled, we want command calls to return NOAUTH instead of ERR with the error message. Otherwise this reveals that we have disabled the configuration in the server side. Signed-off-by: Binbin <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #1475 +/- ##
============================================
+ Coverage 70.86% 70.94% +0.08%
============================================
Files 119 120 +1
Lines 64852 65004 +152
============================================
+ Hits 45958 46120 +162
+ Misses 18894 18884 -10
|
Signed-off-by: Binbin <[email protected]>
Signed-off-by: Binbin <[email protected]>
Signed-off-by: Binbin <[email protected]>
I don't think it's a breaking change since it is moving from error -> error case. I would just list it as a release. I'm also OK with the change atm, but it looks like there are still some tests that need to get fixed. |
Signed-off-by: Binbin <[email protected]>
Maybe we should leave this until 9.0 though, just so that we have the safer boundary of the major version to claim we are making a behavior change. I agree that it makes sense to raise the security bar, but I don't think it's all that important if it's in 8.1 or 9.0. |
ok, let move it to 9.0 |
When requirepass is enabled, we want command calls to return NOAUTH
instead of ERR with the error message.
Previously, these checks were all before the auth check:
This may expose information such as whether the server supports the
command, whether the configuration item is enabled, etc. This is more
of a consistency issue as the same error message is returned when
requirepass is enabled, not a security issue.
This is a behavior change, though perhaps not a breaking one.