Certificates are "expired" temporarily immediately after signing if clocks are not fully accurate #4

New Issue

Closed

opened 2023-09-27 14:59:32 +00:00 by core · 1 comment

core commented

2023-09-27 14:59:32 +00:00

Owner

Since trifid-api creates certificates that are valid starting at the current server time, if devices are behind it can cause them not to recognize the certificate as valid and exit.

Since trifid-api creates certificates that are valid starting at the current server time, if devices are behind it can cause them not to recognize the certificate as valid and exit.

core added the

labels 2023-09-27 14:59:32 +00:00

core self-assigned this 2023-09-27 14:59:32 +00:00

core added this to the trifid-api project 2023-09-27 14:59:32 +00:00

core added this to the trifid-api 0.2.2 milestone 2023-09-27 15:00:14 +00:00

core referenced this issue from a commit

2023-09-29 01:48:37 +00:00

[fix] issue certs that have already been valid for a little bit (1 hour) #4

core referenced this issue

2023-09-29 01:49:50 +00:00

[fix] issue certs that have already been valid for a little bit (1 hour) #4 #5

core referenced this issue from a commit

2023-09-29 01:52:09 +00:00

[fix] issue certs that have already been valid for a little bit (1 hour) #4

core commented

2023-09-29 01:53:46 +00:00

Author

Owner

Fixed by #5.

Fixed by #5.

core closed this issue

2023-09-29 01:53:46 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

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: core/trifid#4

No description provided.