| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | asn1: merge invalid generalized time tests into invalid time tests | joshua | 2025-05-22 | 1 | -16/+10 |
| | | | | | | | | | | | | Previously, invalid generalized time tests were split into a separate set of test vectors and a flag was used when calling the test function to indicate they should be tested as generalized only. This simplifies the code a bit, and makes converting to the new test framework easier. ok jsing | ||||
| * | asn1time: indicate which comparison function failed | tb | 2024-07-21 | 1 | -4/+7 |
| | | | | | extracted from a diff by Kenjiro Nakayama | ||||
| * | Eliminate last timegm() correctly this time | tb | 2024-05-25 | 1 | -5/+25 |
| | | | | | | Also add a test case with a generalized time representing the moment one second past the 32-bit epoch wrap. | ||||
| * | Revert previous | tb | 2024-05-25 | 1 | -10/+4 |
| | | | | | It wasn't quite right, but I also think the test is bogus. | ||||
| * | asn1time: another use of gmtime was hiding here | tb | 2024-05-25 | 1 | -4/+10 |
| | | |||||
| * | Make ASN1_TIME_set_string_X509 and ASN1_TIME_set_string match the man page | beck | 2024-04-08 | 1 | -5/+45 |
| | | | | | | | | | | | | This makes it where people can't put dumb values in certs without trying harder, and changes the regress to test this. GENERALIZED times outside of the RFC5280 spec are required for OCSP but these should be constructed with the GENERALIZED time string setters. ok tb@ | ||||
| * | asn1time: remove some debugging code | tb | 2024-02-18 | 1 | -3/+1 |
| | | |||||
| * | Tweak previous | tb | 2024-02-18 | 1 | -7/+6 |
| | | |||||
| * | Adjust regress test for memset() requested by jsing on review | tb | 2024-02-18 | 1 | -4/+18 |
| | | |||||
| * | Add regress coverage for the new API | tb | 2024-02-18 | 1 | -1/+195 |
| | | | | | | This exercises the new API, in particular with respect to overflow behavior around the years 0/9999, which are special for GeneralizedTime/X.509. | ||||
| * | Add regress coverage for ASN1_UTCTIME_cmp_time_t() | tb | 2023-10-05 | 1 | -5/+12 |
| | | |||||
| * | Add some coverage for ASN1_TIME_cmp_time_t() as well | tb | 2023-10-02 | 1 | -1/+14 |
| | | | | | | ASN1_UTCTIME_cmp_tim_t() could be done similarly, but then I have to mess with LIBRESSL_INTERNAL. Let's do this after unlock. | ||||
| * | Add regress coverage for ASN1_TIME_compare() | tb | 2023-10-02 | 1 | -1/+78 |
| | | |||||
| * | Minor asn1time tweaks | tb | 2023-10-02 | 1 | -26/+12 |
| | | | | | Sprinkle some (static) const and garbage collect an unused struct. | ||||
| * | Ensure no memory is leaked after passing NULL to ASN1_TIME_normalize()libressl-v3.8.1 | job | 2023-08-30 | 1 | -1/+4 |
| | | | | | OK tb@ | ||||
| * | Convert from %i to %d | tb | 2022-09-05 | 1 | -29/+29 |
| | | |||||
| * | cast time_t to long long before printing for portability | tb | 2022-09-05 | 1 | -2/+2 |
| | | |||||
| * | cope with ASN1_TIME_set_string_X509() rename | anton | 2022-07-05 | 1 | -3/+3 |
| | | |||||
| * | Add valid time test from ruby regress, and check ASN1_time_to_tm | beck | 2022-06-30 | 1 | -1/+27 |
| | | | | | against recorded time value. | ||||
| * | add valid utc time that should fail to parse as generalized | beck | 2022-06-30 | 1 | -2/+6 |
| | | |||||
| * | Add tests for times missing seconds, and to be able to test | beck | 2022-06-30 | 1 | -3/+43 |
| | | | | | invalid generalized times specifically | ||||
| * | Add new time manipulation funcitons that OpenSSL has exposed that | beck | 2022-06-27 | 1 | -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() | jsing | 2021-12-09 | 1 | -1/+2 |
| | | |||||
| * | initialize pointer to avoid undefined free on failure | bcook | 2015-12-28 | 1 | -2/+2 |
| | | | | | ok beck@ | ||||
| * | Missing initializer; spotted by coverity. | miod | 2015-10-25 | 1 | -2/+2 |
| | | |||||
| * | Extend tests to call ASN1_{GENERALIZED,UTC,}TIME_set_string() with a NULL | jsing | 2015-10-22 | 1 | -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 testing | jsing | 2015-10-22 | 1 | -2/+2 |
| | | | | | ASN1_UTCTIME_set_string() twice instead. | ||||
| * | Change regress to not believe legacy times are valid | beck | 2015-10-19 | 1 | -65/+4 |
| | | |||||
| * | Add another invalid time, which is currently accepted. | jsing | 2015-10-02 | 1 | -1/+4 |
| | | |||||
| * | Add DER encoding/decoding coverage for ASN.1 GENERALIZEDTIME and UTCTIME. | jsing | 2015-09-25 | 1 | -39/+158 |
| | | |||||
| * | Add initial regress tests for ASN.1 times. | jsing | 2015-09-25 | 1 | -0/+349 |
 |
index : openbsd | |
| A mirror of https://github.com/libressl/openbsd.git |
| summaryrefslogtreecommitdiff |