asn1: use ASN1_TIME_to_tm() to decode UTCTime and GeneralizedTime #974
+117
−106
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.
The current logic relies on
sscanf()and error checks are almost entirely missing. It also assumes thatASN1_STRINGcontents are NUL-terminated, which is undocumented and not guaranteed for all validASN1_TIMEobjects.Switch to using
ASN1_TIME_to_tm()added in OpenSSL 1.1.1. It is also supported by LibreSSL and AWS-LC.In the long term, we may want to replace
ASN1_TIME_to_tm()with a hand-rolled decoder, since the function is intended for a specific use-case. It is too permissive for strict DER, yet still does not support all valid DER inputs and silently drops information such as fractional seconds. However, it handles everything that the currentsscanf()code could handle.Partially resolves #725.