Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Client spec: Timestamp verification should be best effort, not hard fail #16

Open
haydentherapper opened this issue Aug 27, 2024 · 0 comments
Open

Client spec: Timestamp verification should be best effort, not hard fail #16

haydentherapper opened this issue Aug 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@haydentherapper
Copy link

Description

Clients should find as many timestamps as they can from the provided sources (RFC 3161 signed timestamps and log SETs currently). If any one timestamp fails to verify, clients should continue. Clients should only fail if no timestamp can be verified (#15).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haydentherapper