Skip to content

fix: use protected Date header for signed messages #6642

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

Merged
merged 1 commit into from
Mar 16, 2025

Conversation

link2xt
Copy link
Collaborator

@link2xt link2xt commented Mar 11, 2025

Partially addresses #6641

@link2xt link2xt force-pushed the link2xt/receiver-protected-date branch from e9e1c3d to 8d81cb6 Compare March 12, 2025 15:29
@link2xt link2xt force-pushed the link2xt/receiver-protected-date branch 2 times, most recently from 3fa1ec9 to 98afa2d Compare March 16, 2025 07:15
@link2xt link2xt marked this pull request as ready for review March 16, 2025 07:16
@link2xt link2xt force-pushed the link2xt/receiver-protected-date branch 2 times, most recently from df0ac1d to c07b5c9 Compare March 16, 2025 07:21
@link2xt link2xt changed the title fix: use protected Date header when available fix: use protected Date header for signed messages Mar 16, 2025
@link2xt link2xt requested a review from iequidoo March 16, 2025 07:23
@link2xt link2xt requested a review from Hocuri March 16, 2025 13:37
@link2xt link2xt force-pushed the link2xt/receiver-protected-date branch from c07b5c9 to ef008d4 Compare March 16, 2025 16:10
@link2xt link2xt merged commit ef008d4 into main Mar 16, 2025
18 checks passed
@link2xt link2xt deleted the link2xt/receiver-protected-date branch March 16, 2025 16:10
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.

2 participants