Ian Roberts 9abdb1fffb feat: new rule type specifically for signature checks ... Move the signature checking rules out of MatchRule into their own dedicated SignatureRule, configured as "check-signature" in the hooks file. This takes an algorithm, secret and Argument giving the source of the signature, and by default behaves exactly like the old payload-hmac-<algorithm> match rules. However it can also take a second optional Argument to customize how to generate the "string to sign", allowing signatures to be computed over something other than the full request body content. This could be a single header or payload item but more likely will be a "template" argument to combine items from different places in the request, such as the body content and one or more headers, e.g. to compute a signature over the X-Request-Id header, Date header, and request body, concatenated with CRLF, you could specify check-signature: algorithm: sha512 secret: 5uper5eecret signature: source: header name: X-Hook-Signature string-to-sign: source: template name: | {{- printf "%s\r\n" (.GetHeader "x-request-id") -}} {{- printf "%s\r\n" (.GetHeader "date") -}} {{- .BodyText -}}		2024-10-29 20:51:38 +00:00
..
hook.go	feat: new rule type specifically for signature checks	2024-10-29 20:51:38 +00:00
hook_test.go	feat: new rule type specifically for signature checks	2024-10-29 20:51:38 +00:00
request.go	Update GH actions and dependencies (#681)	2024-04-13 12:27:49 +02:00