summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto/aead (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fix error messagetb2023-09-281-2/+2
|
* Check that EVP_CIPHER_CTX_iv_length() matches what was settb2023-09-281-1/+9
| | | | | | This really only covers AES-GCM. From beck
* fixup for MS compilersbcook2023-07-071-1/+8
|
* Test EVP_chacha20_poly1305() (linking statically for now)jsing2022-08-202-3/+4
|
* Update copyright for additional/new code.jsing2022-07-301-1/+2
|
* Provide additional AEAD test cases.jsing2022-07-306-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.jsing2022-07-301-1/+3
|
* Allow the AEAD to be specified for a test file.jsing2022-07-302-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.jsing2022-07-301-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.jsing2022-07-301-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.jsing2022-07-301-4/+4
|
* Less #ifndef OPENSSL_NO_*jsing2022-07-301-17/+1
| | | | | We're not going to be compiling without AES or CHACHA/POLY1305 anytime soon.
* Fix comment formatting.jsing2022-07-301-4/+7
|
* Switch to ISC license.jsing2022-07-301-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.
* Undo static linking and other workarounds that are no longer neededtb2022-01-141-4/+3
| | | | after the bump
* Rework test to use EVP_AEAD_CTX_{new,free}() and link statically for nowtb2022-01-122-20/+32
|
* add support for xchacha20 and xchacha20-poly1305dlg2019-01-222-2/+20
| | | | | | | xchacha is a chacha stream that allows for an extended nonce, which in turn makes it feasible to use random nonces. ok tb@
* Add missing $OpenBSD$ markers.tb2018-07-172-0/+2
|
* Remove chacha20-poly1305-old regress and test vectors.jsing2017-08-282-627/+0
|
* Update AEAD regress to match EVP_aead_chacha20_poly1305() changes.jsing2016-04-282-83/+83
|
* After opening an AEAD, ensure that the decrypted output matches thejsing2016-04-131-0/+5
| | | | plaintext for the regress test case.
* Add EVP_aead_chacha20_poly1305_ietf() - The informational RFC 7539,reyk2015-11-022-0/+42
| | | | | | | | | "ChaCha20 and Poly1305 for IETF Protocols", introduced a modified AEAD construction that is incompatible with the common style that has been already used in TLS with EVP_aead_chacha20_poly1305(). The IETF version also adds a constant (salt) that is prepended to the nonce. OK mikeb@ jsing@
* Wrong logic; Coverity CID 78894miod2015-02-151-1/+1
|
* Include -DLIBRESSL_INTERNAL in regress makefiles.jsing2014-07-081-2/+2
| | | | ok miod@
* Build these tests with WARNINGS=Yes and -Werror, and do the necessarymiod2014-06-011-1/+3
| | | | fixes to keep building.
* Update the aead regress to work with the improved EVP AEAD API.jsing2014-05-261-22/+14
|
* Add additional chacha20-poly1305 test vectors.jsing2014-05-152-10/+620
| | | | Thanks to Piotr Sikora for providing a reference to the source.
* Add chacha20-poly1305 test vector to regress.jsing2014-05-152-5/+24
|
* KNF.jsing2014-05-151-6/+7
|
* Add a regress test for AEAD, based on Adam Langley's code.jsing2014-05-153-0/+413