Skip to content

Conversation

@jacobweinstock
Copy link

Use additional headers in the signature payload:

This will allow users to use headers in the signature payload during the verification process. For example, a timestamp header can be used to validate if requests have been sent recently and reduce the risk of message replays.

Fixes: #643

This will allow users to use headers in the signature
payload during the verification process. For example,
a timestamp header can be used to validate if requests
have been sent recently and reduce the risk of message
replays.

Signed-off-by: Jacob Weinstock <[email protected]>
The range body will not execute if the len
of r.Parameter.SignaturePayloadHeaders is 0.

Signed-off-by: Jacob Weinstock <[email protected]>
Cover the Evaluate func with additional headers
for sha1, sha256, sha512.

Signed-off-by: Jacob Weinstock <[email protected]>
@jacobweinstock jacobweinstock marked this pull request as ready for review June 9, 2023 22:27
Dependencies were old.

Signed-off-by: Jacob Weinstock <[email protected]>
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

Successfully merging this pull request may close these issues.

Allow additional headers to be part of the signature payload

1 participant