ssh-key: use u64
type for certificate timestamps
#209
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #174
Previously certificates only supported the
i64
range to allow for infallible conversions to/fromSystemTime
.Unfortunately OpenSSH defaults to using
u64::MAX
as thevalid_before
time in order to represent certificate that's valid "forever". The previous restriction meant thatssh-key
was incapible of parsing such certificates.This commit switches to using a raw
u64
everywhere, and changing conversions toSystemTime
to return anOption<SystemTime>
which isNone
if theu64
value overflows ani64
.