Skip to content
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

gitea push hook secret comes from the payload not a form #34

Open
jstrachan opened this issue Jul 4, 2019 · 4 comments
Open

gitea push hook secret comes from the payload not a form #34

jstrachan opened this issue Jul 4, 2019 · 4 comments

Comments

@jstrachan
Copy link

just tried gitea's push webhook handling and it looks like the secret comes in via the json payload rather than via a form.

PR on its way...

@bradrydzewski
Copy link
Member

bradrydzewski commented Jul 7, 2019

The secret was deprecated in favor of using the hmac signature in the header to verify authenticity. One of the gitea maintainers recently submitted a pull request to support hmac verification, with a fallback to reading the secret. See #24.

jstrachan pushed a commit to jstrachan/go-scm that referenced this issue Oct 7, 2019
fix: add support for get PRs to bitbucket cloud
@tboerger
Copy link
Contributor

Can we close this issue?

@ashwilliams1
Copy link

I think this remains an open issue. The secret should come from the payload, but the current implementation gets the value from a URL query parameter (via req.FormValue) which is Drone-specific. I think this may also require an update to the Gitea webhook creation code.

@tboerger
Copy link
Contributor

But the secret had been deprecated in favor of the hmac signature?

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

No branches or pull requests

4 participants