-
Notifications
You must be signed in to change notification settings - Fork 791
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
fix(server): isOverDataLimit logic to stop allowing 0 traffic byte #1556
Conversation
issue #1515 This if statement is just wrong and doesn't block access when traffic limit is set to 0 byte. This one character fixes it. Now if we create a new access key, set the limit to 0 before first usage, the client no longer will be able to connect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mind adding or updating our tests for enforceAccessKeyDataLimits
to cover this scenario (where === also disables)? That will help prevent regressions in future refactors.
I can't be a contributor. would you do it |
No problem. I added the requested changes to the PR. |
Merged and we'll try and get this released soon. Thanks again for your contribution @cornzzy! |
issue #1515
This if statement is just wrong and doesn't block access when traffic limit is set to 0 byte. This one character fixes it.
Now if we create a new access key, set the limit to 0 before the first usage, the client no longer will be able to connect as expected.