Feat/GitHub webhook signatures - #370
Open
kuzaxak wants to merge 2 commits into
Open
Conversation
added 2 commits
August 20, 2026 11:34
Let administrators create and revoke shared secrets for incoming webhooks. Encrypt secret values at rest with Packeton’s existing encrypted_text DBAL type, reveal generated values only once, and use Symfony form validation and CSRF protection for management actions.
Add a public GitHub organization webhook endpoint that authenticates the raw request body with X-Hub-Signature-256 before scheduling package updates. Support secret rotation, ignore non-push events safely, retain the legacy token endpoint, and document the new setup flow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a public GitHub organization webhook endpoint that authenticates the raw request body with X-Hub-Signature-256 before scheduling package updates.
Support secret rotation, ignore non-push events safely, retain the legacy token endpoint, and document the new setup flow.