summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto/base64 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Convert from %i to %dtb2022-09-051-9/+9
|
* Plug memory leak reported by Ilya Shipitsintb2021-03-211-3/+2
| | | | | Since r1.7, input in base64_decoding_test() is allocated unconditionally, so free it unconditionally.
* Import openssl-1.1.1d test data to base64test.cinoguchi2020-03-101-1/+97
| | | | ok bcook@ tb@
* Modify regress base64test.cinoguchi2020-03-101-11/+14
| | | | | | | | | | | | | | | | | | | | | | | - Don't remove multi line CR/LF from bt->out when NL mode base64_encoding_test removes CR/LF from bt->out to compare with the encoding result. This is fine with NO NL mode, but it goes wrong with NL mode if encoding result is larger than 64 and multi line, like below. "eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4\neHh4eHh4eHh4eHh4\n" - Use memcpy instead of asprintf to avoid lost '\0' at the end of data This test data loses trailing '\0' if using asprintf. "\x61\x47\x56\x73\x62\x47\x38\x3d\x0a\x00" - Print original data if decoding result comparison fails This change is not for importing test data, but I just notice. It prints bt->out if fail to memcmp bt->in with decoding result. ok bcook@ tb@
* check for asprintf failing allocationderaadt2019-06-271-1/+4
|
* Add missing $OpenBSD$ markers.tb2018-07-171-0/+1
|
* Pull in <sys/types.h> to get ssize_t or <stdint.h> to get uint32_t, instead ofmiod2015-10-301-0/+1
| | | | | relying upon previously included headers to do this, to enhance portability; from Pascal Cuoq, libressl github pull request #52
* 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.
* Fix various issues that result in compiler warnings.jsing2014-05-161-13/+14
| | | | Prompted by a diff from Brent Cook.
* 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-032-0/+380