Skip to content

Constant-time comparison for hook signature (#12) #13

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

Closed
wants to merge 1 commit into from

Conversation

rjz
Copy link
Collaborator

@rjz rjz commented Aug 30, 2015

Using a straightforward boolean equality check for the hook signature opens a small vector for timing attacks; forcing constant-time comparison closes it up.

Using a straightforward boolean equality check for the hook signature
opens a small vector for timing attacks; forcing constant-time
comparison closes it up.
@matthauck
Copy link

Wow, it's been over a year -- why hasn't this PR been merged in? This is a totally valid PR and adheres github's own advice: https://developer.github.com/webhooks/securing/

@rvagg
Copy link
Owner

rvagg commented Jun 27, 2016

Wow, it's been over a year -- why hasn't this PR been merged in?

A bit more politeness to the people providing you with _free_ code would probably be in order here. Generally a "ping" is considered best when trying to get attention on issues that look stale but easily resolvable. Grow some manners or go away @matthauck, I have better things to do than deal with ungrateful and entitled devs.

@rvagg
Copy link
Owner

rvagg commented Jun 27, 2016

@rjz thanks for the patch, it's a pretty tiny vector but I'll buy it anyway. Sorry for missing this and the long delay, published as v0.5.1, I hope it's still helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants