[GH-ISSUE #31] Optional timestamp check during CSR submission #25

Open
opened 2026-02-26 03:33:31 +03:00 by kerem · 0 comments
Owner

Originally created by @laurivosandi on GitHub (Jul 2, 2017).
Original GitHub issue: https://github.com/laurivosandi/certidude/issues/31

Clock skew issues are common, it would be convenient to supply client timestamp with CSR so server could inform CA administrator about the clock skew on client side eg. simply via log entry.

HTTP request header Date should be suitable for this purpose.

Originally created by @laurivosandi on GitHub (Jul 2, 2017). Original GitHub issue: https://github.com/laurivosandi/certidude/issues/31 Clock skew issues are common, it would be convenient to supply client timestamp with CSR so server could inform CA administrator about the clock skew on client side eg. simply via log entry. HTTP request header Date should be suitable for this purpose.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/certidude-laurivosandi#25
No description provided.