Securing your webhooks

Once your server is configured to receive payloads, it'll listen for any payload sent to the endpoint you configured. For security reasons, you probably want to limit requests to those coming from GitHub. There are a few ways to go about this--for example, you could opt to whitelist requests from GitHub's IP address--but a far easier method is to set up a secret token and validate the information.

Setting your secret token

You'll need to set up your secret token in two places: GitHub and your server.

To set your token on GitHub:

Navigate to the repository where you're setting up your webhook.

Fill out the Secret textbox. Use a random string with high entropy (e.g., by taking the output of ruby -rsecurerandom -e 'puts SecureRandom.hex(20)' at the terminal).

Click Update Webhook.

Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running:

export SECRET_TOKEN=your_token

Never hardcode the token into your app!

Validating payloads from GitHub

When your secret token is set, GitHub uses it to create a hash signature with each payload.

This hash signature is passed along with each request in the headers as X-Hub-Signature. Suppose you have a basic server listening to webhooks that looks like this:

The goal is to compute a hash using your SECRET_TOKEN, and ensure that the hash from GitHub matches. GitHub uses an HMAC hexdigest to compute the hash, so you could change your server to look a little like this:

Obviously, your language and server implementations may differ than this code. There are a couple of very important things to point out, however:

No matter which implementation you use, the hash signature starts with sha1=, using the key of your secret token and your payload body.

Using a plain == operator is not advised. A method like secure_compare performs a "constant time" string comparison, which renders it safe from certain timing attacks against regular equality operators.