openbsd/src/regress/lib/libcrypto/asn1, branch OPENBSD_5_9_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_5_9_BASE 2015-12-28T14:18:38+00:00 initialize pointer to avoid undefined free on failure 2015-12-28T14:18:38+00:00 bcook 2015-12-28T14:18:38+00:00 urn:sha1:5bf29cb43d200f029aee6412210176a088b66b2c ok beck@ Add explicit LL suffixes to the numerical constants which do not fit in 32 bits. 2015-10-30T15:52:55+00:00 miod 2015-10-30T15:52:55+00:00 urn:sha1:8f47b4b925f4206e3dfff54c2777c243299f0e44 Missing initializer; spotted by coverity. 2015-10-25T11:59:37+00:00 miod 2015-10-25T11:59:37+00:00 urn:sha1:991aadf92bf4eaaff00372d589c1629eb1909695 Extend tests to call ASN1_{GENERALIZED,UTC,}TIME_set_string() with a NULL 2015-10-22T14:10:55+00:00 jsing 2015-10-22T14:10:55+00:00 urn:sha1:da68d0ffcc517d0ce4f0f46a090f950062525ef1 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 2015-10-22T14:01:19+00:00 jsing 2015-10-22T14:01:19+00:00 urn:sha1:dba45550e6e6a501d95de421da1168ea0bc574a0 ASN1_UTCTIME_set_string() twice instead. Change regress to not believe legacy times are valid 2015-10-19T16:29:22+00:00 beck 2015-10-19T16:29:22+00:00 urn:sha1:f6cd556833cd27c39fdf689334d6d48f27fe533e Add another invalid time, which is currently accepted. 2015-10-02T15:35:30+00:00 jsing 2015-10-02T15:35:30+00:00 urn:sha1:9e98e8a3921fd298877140c939a2a8521d1638b4 Fix a bug in the regress, and be much more pedantic about what is allowed 2015-09-30T14:11:22+00:00 beck 2015-09-30T14:11:22+00:00 urn:sha1:ee59270b8bf6a08f2cca384d16bb223bb3ef2d55 per RFC 5380 in an X509. RFC 5280 states that all times before 2050 must be specified as a UTCtime, not a Generalized time, and all times after must be a UTC time. By extension this also means the smallest time allowed per RFC 5280 is 500101000000Z and the largest is 99991231235959Z.. Add an rfc5280 test suite to test x509_cmp_time. 2015-09-29T04:54:23+00:00 beck 2015-09-29T04:54:23+00:00 urn:sha1:2d95bec5a5f48c4a73965c27a321d89ea569c950 Note some of these will yet fail with the current libcrypto as the current X509_cmp_time is not RFC5280 compliant ok jsing@ Add DER encoding/decoding coverage for ASN.1 GENERALIZEDTIME and UTCTIME. 2015-09-25T17:46:32+00:00 jsing 2015-09-25T17:46:32+00:00 urn:sha1:8f105ff4afbfd0aef9949e96589f185db0e25995