-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Prevent timing attack on CSRF #123
base: master
Are you sure you want to change the base?
Conversation
b547a44
to
1517196
Compare
Hey! Would you mind rebasing on master and removing all |
@tmilewski Hi! Just did that, thanks! |
Prefect, thank you! I’ll try and get this pushed up later today.
Thanks again!
…On Dec 19, 2018, 2:35 PM -0800, Margaret Ma ***@***.***>, wrote:
@tmilewski Hi! Just did that, thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Closing and reopening to trigger CI |
@@ -87,6 +87,16 @@ def app | |||
instance.callback_phase | |||
end | |||
end | |||
|
|||
describe "#secure_params" do |
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.
describe "#secure_params" do | |
describe "#secure_compare" do |
I don't have permission to write to this fork but was wondering if it's possible to get this PR over the line (or the new PR I just opened which resolves the merge conflicts and spec rename) to fix an outstanding security vuln that's also affecting omniauth-auth0 downstream |
use secure_compare instead of plain equality comparison on request and callback state to prevent timing attacks.