asn1time: indicate which comparison function failedextracted from a diff by Kenjiro Nakayama
asn1object: zap trailing whitespace
Make it possible for the large OID test to failfailed was set to 0 at the top of the function, so failure and successwere indistinguishable. Move failed = 0 to the end so it can actuallyfail.
Add regress coverage for some corner cases of i2d_ASN1_OBJECT()
Add regress coverage for i2d_ASN1_OBJECT() fixes
Eliminate last timegm() correctly this timeAlso add a test case with a generalized time representing the momentone second past the 32-bit epoch wrap.
Revert previousIt wasn't quite right, but I also think the test is bogus.
asn1time: another use of gmtime was hiding here
Make ASN1_TIME_set_string_X509 and ASN1_TIME_set_string match the man pageThis makes it where people can't put dumb values in certs withouttrying harder, and changes the regress to test this.GEN
Make ASN1_TIME_set_string_X509 and ASN1_TIME_set_string match the man pageThis makes it where people can't put dumb values in certs withouttrying harder, and changes the regress to test this.GENERALIZED times outside of the RFC5280 spec are required for OCSPbut these should be constructed with the GENERALIZED time stringsetters.ok tb@
show more ...
Link x509_algor test statically and switch to the internalX509_ALGOR_set0_evp_md()
asn1time: remove some debugging code
Tweak previous
Adjust regress test for memset() requested by jsing on review
Add regress coverage for the new APIThis exercises the new API, in particular with respect to overflow behavioraround the years 0/9999, which are special for GeneralizedTime/X.509.
Fix asn1_integer_null_data_test()The failed variable was erroneously initialized to 0, making this testalways pass.From Christian Andersen, thanks!
Remove the string_table testIf it wasn't for security/xca, all of the ASN1_STRING_TABLE API wouldhit the attic before long. API design by a trained professional...The table can at least be made
Remove the string_table testIf it wasn't for security/xca, all of the ASN1_STRING_TABLE API wouldhit the attic before long. API design by a trained professional...The table can at least be made immutable, which in turn makes this testentirely pointless.
Provide prototype for X509_ALGOR_set_md()Once we remove X509_ALGOR_set_md() we can link this test statically and useX509_ALGOR_set_evp_md() but for now make sure the documented workaround forthis
Provide prototype for X509_ALGOR_set_md()Once we remove X509_ALGOR_set_md() we can link this test statically and useX509_ALGOR_set_evp_md() but for now make sure the documented workaround forthis garbage API works.
x509_algor: fix error message
x509_algor: add a few missing includes
x509_algor: Turn expected failure into actual failure now that the API isfixed.
Add preallocation dance for X509_ALGOR_set_md() as documented
Add regress coverage for X509_ALGOR_*This covers the setters and getters. Serialization and deserialization aswell as comparison is already well covered by the pieces of regress usingcerts.Ther
Add regress coverage for X509_ALGOR_*This covers the setters and getters. Serialization and deserialization aswell as comparison is already well covered by the pieces of regress usingcerts.There is currently one printf indicating failure. This will be fixedshortly.
Add regress coverage for ASN1_UTCTIME_cmp_time_t()
Add some coverage for ASN1_TIME_cmp_time_t() as wellASN1_UTCTIME_cmp_tim_t() could be done similarly, but then I have to messwith LIBRESSL_INTERNAL. Let's do this after unlock.
Add regress coverage for ASN1_TIME_compare()
12345