summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto/asn1/asn1time.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Convert from %i to %dtb2022-09-051-29/+29
|
* cast time_t to long long before printing for portabilitytb2022-09-051-2/+2
|
* cope with ASN1_TIME_set_string_X509() renameanton2022-07-051-3/+3
|
* Add valid time test from ruby regress, and check ASN1_time_to_tmbeck2022-06-301-1/+27
| | | | against recorded time value.
* add valid utc time that should fail to parse as generalizedbeck2022-06-301-2/+6
|
* Add tests for times missing seconds, and to be able to testbeck2022-06-301-3/+43
| | | | invalid generalized times specifically
* Add new time manipulation funcitons that OpenSSL has exposed thatbeck2022-06-271-2/+35
| | | | | | | | the world seems to be using. Symbols.list changes and exposure to wait for minor bump ok jsing@ jca@
* Fix missing return in asn1_compare_bytes()jsing2021-12-091-1/+2
|
* initialize pointer to avoid undefined free on failurebcook2015-12-281-2/+2
| | | | ok beck@
* Missing initializer; spotted by coverity.miod2015-10-251-2/+2
|
* Extend tests to call ASN1_{GENERALIZED,UTC,}TIME_set_string() with a NULLjsing2015-10-221-1/+19
| | | | | | | pointer - because, you know, you might want to set a string on a NULL object. The previous implementation apparently allowed this as a way of testing if the string was valid... probably because the *_check() functions are only useable after the string has already been set.
* Fix case where we wanted to test ASN1_TIME_set_string() but were testingjsing2015-10-221-2/+2
| | | | ASN1_UTCTIME_set_string() twice instead.
* Change regress to not believe legacy times are validbeck2015-10-191-65/+4
|
* Add another invalid time, which is currently accepted.jsing2015-10-021-1/+4
|
* Add DER encoding/decoding coverage for ASN.1 GENERALIZEDTIME and UTCTIME.jsing2015-09-251-39/+158
|
* Add initial regress tests for ASN.1 times.jsing2015-09-251-0/+349