5 commits

Author	SHA1	Message	Date
Kurt Roeckx	d69d8f904c	Make the fuzzers more reproducible ... We want to be in the same global state each time we come in FuzzerTestOneInput(). There are various reasons why we might not be that include: - Initialization that happens on first use. This is mostly the RUN_ONCE() things, or loading of error strings. - Results that get cached. For instance a stack that is sorted, RSA blinding that has been set up, ... So I try to trigger as much as possible in FuzzerInitialize(), and for things I didn't find out how to trigger this it needs to happen in FuzzerTestOneInput(). Reviewed-by: Rich Salz <rsalz@openssl.org> GH: #2023	2016-12-03 00:14:15 +01:00
Kurt Roeckx	ad4da7fbc0	Add a FuzzerClean() function ... This allows to free everything we allocated, so we can detect memory leaks. Reviewed-by: Rich Salz <rsalz@openssl.org> GH: #2023	2016-12-03 00:14:14 +01:00
Kurt Roeckx	f3e911d5ed	Fix formatting of fuzzers ... Reviewed-by: Rich Salz <rsalz@openssl.org> GH: #2023	2016-12-03 00:14:14 +01:00
Kurt Roeckx	a05b0bcf87	Re-add x509 and crl fuzzer ... Reviewed-by: Rich Salz <rsalz@openssl.org> GH: #1276	2016-07-01 17:02:33 +02:00
Kurt Roeckx	e1859d8d54	Add X509 and CRL fuzzer ... Reviewed-by: Rich Salz <rsalz@openssl.org> GH: #1229	2016-06-25 11:01:29 +02:00