Adam Langley
|
a081423809
|
Add document about incorporating BoringSSL into a project.
Change-Id: Ia825300bae236e3133dd9a19313b7f5450f0c8e2
Reviewed-on: https://boringssl-review.googlesource.com/7781
Reviewed-by: David Benjamin <davidben@google.com>
|
2016-04-27 18:04:37 +00:00 |
|
David Benjamin
|
5acc423517
|
Add a CONTRIBUTING.md file.
Change-Id: I4e1ed0aaddf4dc516a81155ef62dba138f8495ae
Reviewed-on: https://boringssl-review.googlesource.com/7120
Reviewed-by: Adam Langley <agl@google.com>
|
2016-02-10 21:38:19 +00: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 |
|
David Benjamin
|
03bad147b6
|
Links in README.md, take two.
gitiles seems to mangle the links when viewed from
https://boringssl.googlesource.com/boringssl/+/master/README.md, but not
https://boringssl.googlesource.com/boringssl/.
This document suggests that it handles absolute and relative links to files
specially. I guess it didn't interpret 'README.md' as either and failed to adjust
it accordingly. Let's see if this works instead.
https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md#Links
Change-Id: Ic181919140f968c88c69ea8f3c21c70f63e4b467
Reviewed-on: https://boringssl-review.googlesource.com/6230
Reviewed-by: Adam Langley <agl@google.com>
|
2015-10-13 18:04:43 +00:00 |
|
Adam Langley
|
6a2c512a7b
|
Add a README.
Change-Id: I77b1d0efa6cddfcb162be693d53276822780540f
Reviewed-on: https://boringssl-review.googlesource.com/5790
Reviewed-by: Adam Langley <agl@google.com>
|
2015-10-13 17:52:28 +00:00 |
|