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

timestamp (ts) verification code needs to be updated to RFC 5816 & 5035 #2119

Closed
ldgibbons opened this issue Dec 19, 2016 · 3 comments
Closed

timestamp (ts) verification code needs to be updated to RFC 5816 & 5035 #2119

ldgibbons opened this issue Dec 19, 2016 · 3 comments

Comments

@ldgibbons
Copy link

ldgibbons commented Dec 19, 2016 •
edited

The timestamp (ts) app and crypto are designed to RFCs 3161 & 2634. These RFCs from 2001 and 1999 have been updated by RFCs 5816 & 5035, yet the timestamp code has not kept pace. As a result the current code is unable to verify valid timestamp responses from TSAs which use the newer attributes SigningCertificateV2 and ESSCertIDv2.
@richsalz
Copy link
Contributor

Yes. The TS code is not a priority for the openssl dev team, so if you want it consider making a pull request.

@FdaSilvaYY
Copy link
Contributor

FdaSilvaYY commented Dec 19, 2016 •
edited

See also PR #206 and #771

@richsalz richsalz mentioned this issue May 2, 2017
Closed
@richsalz
Copy link
Contributor

richsalz commented May 3, 2017

Both PR's merged, closing this issue.

@richsalz richsalz closed this as completed May 3, 2017
@richsalz richsalz mentioned this issue Sep 13, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@richsalz @FdaSilvaYY @ldgibbons