boringssl

kris/boringssl

Fork 0

Commit Graph

Author	SHA1	Message	Date
David Benjamin	cd4d981bba	Update the existing corpora for the format change. This was done by prepending each file with kDataTag, or 0x0000. This causes them to behave as they did before the fuzzer updates. Bug: 104 Change-Id: Ic768606911e1310fb59bed647990c237fe15776b Reviewed-on: https://boringssl-review.googlesource.com/17534 Reviewed-by: David Benjamin <davidben@google.com>	2017-07-05 23:48:54 +00:00
David Benjamin	bd672ae8c7	Refresh TLS fuzzer corpora. This was done by first minimizing the existing set and then merging in a fresh recording from runner. Glancing through LCOV output does not reveal anything anomolous. Fuzzer mode seems to be working as expected. Change-Id: Ife0959a5e16e3c7e2e5a2deb0c32539ff2bc740b Reviewed-on: https://boringssl-review.googlesource.com/11229 Reviewed-by: Adam Langley <agl@google.com>	2016-09-22 21:35:16 +00:00

Author

SHA1

Message

Date

David Benjamin

cd4d981bba

Update the existing corpora for the format change.

This was done by prepending each file with kDataTag, or 0x0000. This
causes them to behave as they did before the fuzzer updates.

Bug: 104
Change-Id: Ic768606911e1310fb59bed647990c237fe15776b
Reviewed-on: https://boringssl-review.googlesource.com/17534
Reviewed-by: David Benjamin <davidben@google.com>

2017-07-05 23:48:54 +00:00

David Benjamin

bd672ae8c7

Refresh TLS fuzzer corpora.

This was done by first minimizing the existing set and then merging in a
fresh recording from runner. Glancing through LCOV output does not
reveal anything anomolous. Fuzzer mode seems to be working as expected.

Change-Id: Ife0959a5e16e3c7e2e5a2deb0c32539ff2bc740b
Reviewed-on: https://boringssl-review.googlesource.com/11229
Reviewed-by: Adam Langley <agl@google.com>

2016-09-22 21:35:16 +00:00

2 Commits