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.

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

Unix timestamp bug in x509:setLifetime() and x509:getLifetime() #178

Closed
littlerunavay opened this issue Feb 21, 2020 · 1 comment · Fixed by #179
Closed

Unix timestamp bug in x509:setLifetime() and x509:getLifetime() #178

littlerunavay opened this issue Feb 21, 2020 · 1 comment · Fixed by #179

Comments

@littlerunavay
Copy link

Every time I'm trying to call agetLifetime() function on a certificate with expiration date less then 946684800 01/01/2000 @ 12:00am (UTC) in unix timestamp the function returns 4070908799 12/31/2098 @ 11:59pm (UTC).
The same behaviour noticed for setLifetime() when trying to set valid to date for less then 946684800.

@daurnimator
Copy link
Collaborator

See #179

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants