Skip to content
This repository has been archived by the owner on Jun 30, 2023. It is now read-only.

Update verify_webhook_signature to match more recent security guidelines #9

Merged
merged 1 commit into from
Nov 9, 2021

Conversation

rick
Copy link
Contributor

@rick rick commented Nov 9, 2021

everything-is-super-secure

See:
https://docs.github.com/en/developers/webhooks-and-events/webhooks/securing-your-webhooks

The SHA1 algorithm is no longer being used, favoring SHA256 instead, which requires changing which HTTP header to use (going from X-HUB-Signature to X-HUB-Signature-256).

A secure comparison is used instead of == to help avoid timing attacks.

See: 
  https://docs.github.com/en/developers/webhooks-and-events/webhooks/securing-your-webhooks

The SHA1 algorithm is no longer being used, favoring SHA256 instead, which requires changing which HTTP header to use (going from X-HUB-Signature to X-HUB-Signature-256).
    
A secure comparison is used instead of `==` to help avoid timing attacks.
Copy link
Contributor

@rachmari rachmari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @rick. I'll get this merged ASAP. 🚀

@rachmari rachmari merged commit b429a0c into github-developer:master Nov 9, 2021
@rick rick deleted the patch-1 branch November 9, 2021 21:58
@rick
Copy link
Contributor Author

rick commented Nov 9, 2021

giphy (3)

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

Successfully merging this pull request may close these issues.

2 participants