| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Consistently initialize failure to 1 at the top of the function and | tb | 2022-08-05 | 1 | -76/+62 | |
| | | | | | clear it right before the done label. | |||||
| * | Consistently check for CBB_init() failure. | tb | 2022-08-05 | 1 | -45/+89 | |
| | | ||||||
| * | Remove most of the indirection introduced in previous and instead fetch | tb | 2022-08-05 | 1 | -400/+339 | |
| | | | | | | | | the appropriate tls_extension_funcs pointers for client and server from libssl and reach into them directly. ok jsing | |||||
| * | Add some glue to fetch the tlsext functions from the tls_extensions[] | tb | 2022-08-04 | 1 | -190/+440 | |
| | | | | | table rather than calling the functions directly. | |||||
| * | Update copyright for additional/new code. | jsing | 2022-07-30 | 1 | -1/+2 | |
| | | ||||||
| * | Provide additional AEAD test cases. | jsing | 2022-07-30 | 6 | -1/+1991 | |
| | | | | | | | | | | Bring in additional AEAD test cases from BoringSSL. This provides additional coverage for AES-{128,192,256}-GCM, as well as Chacha20-Poly1305 and XChaCha20-Poly1305. Discussed with tb@ | |||||
| * | Add EVP_aes_192_gcm() as a known AEAD. | jsing | 2022-07-30 | 1 | -1/+3 | |
| | | ||||||
| * | Allow the AEAD to be specified for a test file. | jsing | 2022-07-30 | 2 | -8/+12 | |
| | | | | | | Currently, this must be specified per test - allow it to be given as a command line argument that applies to the entire test file. | |||||
| * | Run AEAD tests against EVP_CIPHER implementations. | jsing | 2022-07-30 | 1 | -15/+220 | |
| | | | | | | | | | In addition to running AEAD tests against the EVP_AEAD implementation, also run them against the EVP_CIPHER implementation where applicable. This is a perfect example of why EVP_AEAD exists and why EVP_CIPHER is completely unsuited for use with AEADs... | |||||
| * | Allow quoted ASCII strings as input for AEAD regress. | jsing | 2022-07-30 | 1 | -21/+42 | |
| | | | | | | | Currently, each line in the text file is expected to be string of hexadecimal digits. In addition to this, allow a line to be given as an quoted ASCII string. | |||||
| * | Sort includes. | jsing | 2022-07-30 | 1 | -4/+4 | |
| | | ||||||
| * | Less #ifndef OPENSSL_NO_* | jsing | 2022-07-30 | 1 | -17/+1 | |
| | | | | | | We're not going to be compiling without AES or CHACHA/POLY1305 anytime soon. | |||||
| * | Fix comment formatting. | jsing | 2022-07-30 | 1 | -4/+7 | |
| | | ||||||
| * | Switch to ISC license. | jsing | 2022-07-30 | 1 | -46/+13 | |
| | | | | | | | | Use Google's ISC license for this code - this was originally being upstreamed to OpenSSL by Adam Langley, however it was never actually accepted and eventually ended up in BoringSSL (via commit dfe3053086). The same change was made a long time ago for evp/evp_aead.c and others. | |||||
| * | Add a second test to validate the tables in the library. | tb | 2022-07-28 | 1 | -1/+42 | |
| | | ||||||
| * | Adjust a comment to reflect reality, minor code tweaks. | tb | 2022-07-27 | 1 | -7/+7 | |
| | | ||||||
| * | minor tweaks: unwrap a line, tweak a comment and zap an empty line | tb | 2022-07-26 | 1 | -5/+3 | |
| | | ||||||
| * | Remove test of non-portable implementation details (whether wctype_t | guenther | 2022-07-25 | 1 | -5/+1 | |
| | | | | | | | | and wctrans_t values are locale-specific) so we can simplify our implementation in libc ok schwarze@ | |||||
| * | Add a regression test for bn_isqrt.c | tb | 2022-07-25 | 2 | -1/+302 | |
| | | | | | | This validates the tables used in bn_is_perfect_square() and checks that for randomly generated numbers the isqrt() is what it is expected to be. | |||||
| * | Separate the macro for generating string test functions | schwarze | 2022-07-25 | 1 | -14/+22 | |
| | | | | | | | | | | | for the macro generating test functions for other data types. This makes sense because both are sufficiently different. It also avoids a large number of false positive compiler warnings that guenther@ reported. OK guenther@ | |||||
| * | Extend TLS buffer regress to cover read/write usage. | jsing | 2022-07-22 | 1 | -13/+219 | |
| | | ||||||
| * | Make test table based, extend it a little | tb | 2022-07-21 | 1 | -69/+117 | |
| | | ||||||
| * | link ssl_set_alpn_protos to regress | tb | 2022-07-20 | 1 | -1/+2 | |
| | | ||||||
| * | Add a quick and dirty regress for SSL{_CTX,}_set_alpn_protos() | tb | 2022-07-20 | 1 | -0/+156 | |
| | | ||||||
| * | zap trailing spaces | tb | 2022-07-19 | 1 | -2/+2 | |
| | | ||||||
| * | Regenerate golden numbers due to RC4-MD5 now being disabled by default. | tb | 2022-07-19 | 1 | -61/+58 | |
| | | ||||||
| * | Revert accidental commit | tb | 2022-07-18 | 1 | -2/+2 | |
| | | ||||||
| * | Add comments to explain the magic numbers 57 and 58 | tb | 2022-07-18 | 2 | -3/+6 | |
| | | ||||||
| * | Avoid sending the QUIC transport parameters extension now that we | tb | 2022-07-18 | 1 | -4/+4 | |
| | | | | | | | send an unsupported extension alert. Noted by anton | |||||
| * | Revise regress for QUIC transport parameters TLS extension. | jsing | 2022-07-17 | 1 | -15/+32 | |
| | | ||||||
| * | Revert previous. The added includes were already there. Duh. | tb | 2022-07-16 | 1 | -4/+1 | |
| | | ||||||
| * | Enable Wycheproof primality tests. | tb | 2022-07-13 | 2 | -4/+4 | |
| | | ||||||
| * | The asn1time test no longer needs static linking. | tb | 2022-07-12 | 1 | -4/+1 | |
| | | ||||||
| * | Check that ASN1_{INTEGER,ENUMERATED}_get(NULL) return 0 as documented. | tb | 2022-07-09 | 1 | -1/+22 | |
| | | ||||||
| * | whitespace | tb | 2022-07-08 | 1 | -3/+3 | |
| | | ||||||
| * | Add to variables instead of overriding them | tb | 2022-07-08 | 1 | -4/+4 | |
| | | ||||||
| * | Add support for primality checking | tb | 2022-07-07 | 4 | -10/+218 | |
| | | | | | | | | | | | | | | Project Wycheproof's primality_tests.json contain a set of 280 numbers that trigger edge cases in Miller-Rabin and related checks. libcrypto's Miller-Rabin test is known to be rather poor, hopefully we will soon see a diff on tech that improves on this. This extends the Go test in the usual way and also adds a perl script that allows testing on non-Go architectures. Deliberately not yet linked to regress since the tests are flaky with the current BN_is_prime_ex() implementatation. | |||||
| * | Use the security level knob in the test script. | tb | 2022-07-07 | 1 | -2/+14 | |
| | | | | | from beck | |||||
| * | Only run tests against ciphers supported by the method. | tb | 2022-07-07 | 2 | -4/+28 | |
| | | ||||||
| * | Add some minimal regress coverage for the security level. | tb | 2022-07-07 | 1 | -1/+6 | |
| | | | | | From beck | |||||
| * | Make the ssltest security level aware. | tb | 2022-07-07 | 1 | -1/+9 | |
| | | | | | From beck | |||||
| * | Switch ssltest to using the newly generated certs that use SHA-256 instead | tb | 2022-07-07 | 2 | -8/+6 | |
| | | | | | | | of SHA-1. This helps the switch to security-level aware ssltest. From jsing | |||||
| * | cope with ASN1_TIME_set_string_X509() rename | anton | 2022-07-05 | 1 | -3/+3 | |
| | | ||||||
| * | Adjust to new tls1_ec_nid2group_id API. | tb | 2022-07-02 | 1 | -7/+13 | |
| | | ||||||
| * | 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 support for sending QUIC transport parameters | beck | 2022-06-29 | 1 | -1/+257 | |
| | | | | | | | | | | | This is the start of adding the boringssl API for QUIC support, and the TLS extensions necessary to send and receive QUIC transport data. Inspired by boringssl's https://boringssl-review.googlesource.com/24464 ok jsing@ tb@ | |||||
| * | Use relative paths so beck can run regress in his git tree and have | tb | 2022-06-29 | 4 | -8/+12 | |
| | | | | | the correct ssl_local.h etc be picked up. | |||||
| * | Botan 2.19.2 has removed support for the OpenSSL crypto provider. | bluhm | 2022-06-28 | 2 | -24/+1 | |
| | | | | | | | | It was incompatible with OpenSSL 3.0. Remove the regression test to check that LibreSSL crypto works with Botan tests. This is better than to keep an outdated Botan in ports. discussed with tb@ beck@ | |||||
 |
index : openbsd | |
| A mirror of https://github.com/libressl/openbsd.git |
| summaryrefslogtreecommitdiff |