You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Delete unnecessary files and fix format in some MD pages (#4115)
* style: Clean up the repo
* Bolster the `.gitignore`
* Follow `CONTRIBUTING.md` guidelines and wrap `README.md` to 80
characters and seperate links for readability
* Remove pesky Unicode dash in `CONTRIBUTING.md`
* Remove `.DS_STORE` files
* Rename `#project.yaml#` to something logical and enable stntax
highlighting
* Updates from reviewers
* Greatly reduce `.gitignore` to only macOS `.DS_Store` and Vim
temporary files
* Apply markdown style to `docs/index.md`
* small comma grammatical change
* http -> https
# OSS-Fuzz: Continuous Fuzzing for Open Source Software
2
2
3
-
[Fuzz testing](https://en.wikipedia.org/wiki/Fuzz_testing) is a well-known
4
-
technique for uncovering programming errors in software.
5
-
Many of these detectable errors, like [buffer overflow](https://en.wikipedia.org/wiki/Buffer_overflow), can have serious security implications. Google has found [thousands] of security vulnerabilities and stability bugs by deploying [guided in-process fuzzing of Chrome components](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html),
6
-
and we now want to share that service with the open source community.
7
-
3
+
[Fuzz testing] is a well-known technique for uncovering programming errors in
4
+
software. Many of these detectable errors, like [buffer overflow], can have
5
+
serious security implications. Google has found [thousands] of security
6
+
vulnerabilities and stability bugs by deploying [guided in-process fuzzing of
7
+
Chrome components], and we now want to share that service with the open source
* 2016-12-01 - [Announcing OSS-Fuzz: Continuous fuzzing for open source software]
53
+
* 2017-05-08 - [OSS-Fuzz: Five months later, and rewarding projects]
54
+
* 2018-11-06 - [A New Chapter for OSS-Fuzz]
37
55
38
-
* 2016-12-01 - [Announcing OSS-Fuzz: Continuous fuzzing for open source software](https://opensource.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html)
39
-
* 2017-05-08 - [OSS-Fuzz: Five months later, and rewarding projects](https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html)
40
-
* 2018-11-06 - [A New Chapter for OSS-Fuzz](https://security.googleblog.com/2018/11/a-new-chapter-for-oss-fuzz.html)
56
+
[Announcing OSS-Fuzz: Continuous fuzzing for open source software]: https://opensource.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html
57
+
[OSS-Fuzz: Five months later, and rewarding projects]: https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html
58
+
[A New Chapter for OSS-Fuzz]: https://security.googleblog.com/2018/11/a-new-chapter-for-oss-fuzz.html
0 commit comments