-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Backport CVE-2019-5421 fix to 3.x #5043
Backport CVE-2019-5421 fix to 3.x #5043
Conversation
Backported from heartcombo#4996
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.
oops...
initial_failed_attempts = user.failed_attempts | ||
same_user = User.find(user.id) | ||
|
||
user.valid_for_authentication?{ false } |
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.
Just out of curiosity, what's the benefit of calling #valid_for_authentication?
instead of #user.increment_failed_attempts
?
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.
Afaik increment_failed_attempts
is not available in the 3-stable
branch.
The incrementation is actually done in the valid_for_authentication?
method
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.
Oh, that's correct. That's my bad, sorry 😞
is there a timeline for when this fix will be released? |
@dy-cs There are no plans to release a version since 3.x is not officially maintained anymore. We do accept those backport pull requests so that people can grab the Gem directly from GitHub pointing to the |
@tegon gotcha. thanks for the reply! |
See #4996