You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
As the default scheme is to include the Date header in the signature, service providers SHOULD protect against logged replay attacks by enforcing a clock skew. The server SHOULD be synchronized with NTP, and the recommendation is to allow 300 seconds of clock skew (in either direction).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The http-signature security audit recommends that server implementations validate the required Date header to be within a 5 minutes skew interval.
https://web-payments.org/specs/source/http-signatures-audit/#replay-http
Excerp:
The text was updated successfully, but these errors were encountered: