Curious about how a certificate ends up with 18446744073709546693 in a time field instead of a timestamp:
github.com/GrapheneOS/Aud
The other timestamp fields appear to be fine when this happens. I ran into this problem months ago but I wasn't ready to use the feature yet anyway.
Conversation
Replying to
It does act as a timestamp in milliseconds, and it ended up wrapping around when it reached 2^64. Not sure why it's offset like this. Going to need to keep an eye on it and figure out at which point it jumps back to near the 2^64 range, if ever, since it appears it might cycle.
2