kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
3,351 Commits 12 Branches 0 Tags 38 MiB
99dce54031
Commit Graph

10 Commits

Author SHA1 Message Date
David Benjamin
1991af6900 Refresh TLS fuzzer corpora for draft 16. 
Change-Id: I3476d3ba7cf90e023f6ad2ff9264a31c59a74e6a
Reviewed-on: https://boringssl-review.googlesource.com/11584
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Steven Valdez <svaldez@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
 2016-10-13 19:12:50 +00:00
David Benjamin
4f4e0dda3b Refresh TLS fuzzer corpora. 
Our implementation now expects draft 15.

Change-Id: I261a090763951110a6c9f03acfda4ae23cc14cfc
Reviewed-on: https://boringssl-review.googlesource.com/11502
Reviewed-by: Steven Valdez <svaldez@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
 2016-10-06 15:04:50 +00:00
David Benjamin
0d81373f91 Refresh fuzzer corpus. 
We've switched to the version extension, so refresh the corpus.

Change-Id: Ic50f58bd83d62dccae26063c9ea2d4a2c799da1f
Reviewed-on: https://boringssl-review.googlesource.com/11326
Reviewed-by: Adam Langley <agl@google.com>
 2016-09-27 21:37:49 +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
David Benjamin
88536c3cb1 Start fuzzing the TLS 1.3 code. 
Corpus recorded from runner and merged into existing corpus with
libFuzzer's -merge flag.

BUG=79

Change-Id: I986a50976ffef141b63e31de3a81fdb4ed5c1348
Reviewed-on: https://boringssl-review.googlesource.com/11130
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
 2016-09-21 20:47:15 +00:00
Adam Langley
79c576c0e1 Update fuzzing corpus for ‘server’ 
Change-Id: I95e75708fb758265a28e775025ad748ac505770e
 2016-08-11 08:56:18 -07:00
David Benjamin
58218b63bc Regenerate server_corpus and client_corpus. 
Now that client.cc and server.cc run through application data, regenerate the
corpus.

Change-Id: I8278ebfe47fd2ba74f67db6f9b545aabf9fd1f84
Reviewed-on: https://boringssl-review.googlesource.com/7301
Reviewed-by: Adam Langley <agl@google.com>
 2016-03-04 19:13:32 +00:00
Adam Langley
80c0fd6746 Update fuzzing corpuses. 
This results from running the fuzzers for a little while with both the
8bit-counters change and after taking the transcripts from the runner
tests as seeds for the `client` and `server` fuzzers.

Change-Id: I545a89d8dccd7ef69dd97546ed61610eea4a27a3
Reviewed-on: https://boringssl-review.googlesource.com/7276
Reviewed-by: David Benjamin <davidben@google.com>
 2016-03-03 18:33:05 +00:00
Adam Langley
3202750a98 Update the fuzz tests for the server. 
These seeds are the result of spending more CPU time fuzzing the server.

Change-Id: Iacf889ae6e214056033f4a5f9f3b89e4710c22a5
 2015-12-22 16:35:07 -08:00
Adam Langley
9a4beb8ad8 Add four, basic fuzz tests. 
This change adds fuzzing tests for:
  ∙ Certificate parsing
  ∙ Private key parsing
  ∙ ClientHello parsing
  ∙ Server first flow (ServerHello, Certificate, etc) parsing.

Change-Id: I5f53282263eaaff69b1a03c819cca73750433653
Reviewed-on: https://boringssl-review.googlesource.com/6460
Reviewed-by: Adam Langley <agl@google.com>
 2015-11-10 19:14:01 +00:00