summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Add chacha20-poly1305 test vector to regress.jsing2014-05-152-5/+24
|
* KNF.jsing2014-05-152-47/+50
|
* Add a regress test for AEAD, based on Adam Langley's code.jsing2014-05-153-0/+413
|
* Add poly1305 to libcrypto utilising Andrew Moon's public domainjsing2014-05-143-1/+175
| | | | | | implementation. ok miod@
* Remove AES_bi_ige_encrypt() from libcrypto. This routine is supposed to usemiod2014-05-121-134/+0
| | | | | | | | | | | | | two keys and four IVs to do much magic, is specified as such with test vectors, but the implementation actually always uses the first key, and the test vectors were computed with it, so they are wrong. Fixing the code to match the intended specification would break interoperability with existing code (assuming such code would exist), so it is better to remove this interface, which is obviously too complex for mere mortals if even its author can not implement it correctly. Riding on the libcrypto major bump.
* Move the `pqueue' part of libcrypto, which is a glorified sorted linked listmiod2014-05-122-9/+23
| | | | | | | | | | | | | of 64-bit data, and only used by DTLS, to libssl where it belongs. Remove pqueue_print() which is a debugging interface and serves no useful purpose, except for the regress test, which grows its own pqueue_print() routine. Bump libcrypto major and libssl minor. WARNING: do not update your tree right now, more changes are coming, which will ride the libcrypto major bump.
* Make sure the stdout output is check, to confirm proper sorting.miod2014-05-063-1/+10
|
* Add a fixed (read: non-SIGSEGV'ing) pq_test.miod2014-05-063-1/+111
|
* Update the base64 regress test and enable a test that would previouslyjsing2014-05-031-19/+28
| | | | | | | have resulted in a segfault. Also update the resulting output bytes now that the invalid/corrupt input is detected and rejected; unless you're using BIO_FLAGS_BASE64_NO_NL, in which case you still get a stream of zero value bytes and no way of knowing that the data is invalid/corrupt.
* Initial version of a base64 regress.jsing2014-05-033-1/+382
|
* Simple sha{224,256,384,512} test using the FIPS 180-2 test vectors availablemiod2014-05-022-2/+45
| | | | from http://csrc.nist.gov/groups/ST/toolkit/examples.html
* KNF.jsing2014-05-011-324/+296
|
* Provide an EVP implementation for ChaCha.jsing2014-05-012-0/+17
| | | | ok miod@
* Add ChaCha to libcrypto, based on djb's public domain implementation.jsing2014-05-013-1/+270
| | | | ok deraadt@
* When compiling with AES_WRAP_TEST, make main() return a meaningful valuemiod2014-04-222-1/+14
| | | | | instead of garbage, and add this to the libcrypto regress. Note these tests are incomplete, as they always use the default IV.
* ECDSA signature computation involves a random number. Remove the test trying tomiod2014-04-181-116/+0
| | | | | force what RAND_bytes() will return and comparing it against known values - I can't let you do this, Dave.
* crypto/modes/gcm128.c can be used as its own selftest. Add it to regress,miod2014-04-172-1/+14
| | | | conveniently leaving the benchmark code not compiled in the test.
* Invoke OPENSSL_add_all_algorithms_noconf() to enforce OPENSSL_cpuid_setup()miod2014-04-171-5/+1
| | | | | has been called, for, depending how libcrypto, it might be a hidden symbol. Reported by jsg@
* move enginetest to regress as was done with the other testsjsg2014-04-173-1/+292
|
* adapt to the less old des apijsg2014-04-161-49/+49
|
* Import the OpenSSL libcrypto tests in a form suitable for our rergressmiod2014-04-1548-0/+9639
infrastructure. The following tests have not been imported, for their code lacks a licence: asn1, rsa, sha256, sha512, wp.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-28 08:30:09 +0000