| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| |
|
|
|
| |
* [docs] Add FAQ entry regarding forked repos + bump the bundler version.
* format
|
| |
|
|
|
| |
* Use LABEL in place of MAINTAINER
* Remove LABEL maintainer from Dockerfiles
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Just a follow-up to https://github.com/google/oss-fuzz/pull/3984 that
should address https://github.com/google/oss-fuzz/pull/3984#discussion_r440951881.
According to https://jekyllrb.com/docs/liquid/tags/#code-snippet-highlighting,
another option would be to add `render_with_liquid: false` in your front matter to
disable Liquid entirely for a particular document.
|
| |
|
| |
This was discussed in https://github.com/google/oss-fuzz/pull/3969#discussion_r439145136
|
| | |
|
| |
|
|
|
|
|
| |
This is a follow-up to [this comment][1] which provides some intro docs
for how to get started quickly with a Rust project, explaining `cargo
fuzz` and some basic setup steps.
[1]: https://github.com/google/oss-fuzz/issues/3383#issuecomment-642137449
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Revert "Revert "[CIFuzz] Add support for different sanitizers (#3516)""
This reverts commit c580d0d626247017dede2847869e1eb8a3705ee1.
* cifuzz: pass "sanitizer" to the "run fuzzer" step
It's a follow-up to https://github.com/google/oss-fuzz/pull/3516 that
should fix https://github.com/google/oss-fuzz/issues/3727.
* [cifuzz] drop a $
That's another follow-up to #3516 that should help to pass sanitizer correctly.
Otherwise, it always falls back to address with:
2020-06-11 21:10:14,852 - root - INFO - $address is not a project sanitizer, defaulting to address.
|
| | |
|
| |
|
|
| |
s/allowed_broken_targets_percentage/allowed-broken-targets-percentage/ (#3803)
|
| |
|
|
|
|
|
|
| |
Currently we use Github action's inputs as inputs to cifuzz.
This means we need to do an extra step to convert each input into
an env var so our scripts can actually use it.
This is pretty bug prone and unnecessary, we should probably
get rid of this abstraction and switch to encouraging devs to set
the env vars directly.
|
| |
|
| |
Closes https://github.com/google/oss-fuzz/issues/3711
|
| |
|
|
| |
This reverts commit 9b30127675b0bf295648e2f907df0d756ff5a2eb.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
(#3657)
* [Go] remove "-lpthread" flag from "compile_fuzzer" and fix comments (#2714).
* fix unrelated go-dns and gonids errors
* simplify golang/build.sh as per Abhishek's comment
|
| |
|
|
|
|
|
| |
* Switch OSS projects to use native go-fuzz.
* Fix go-json-iterator breakage, put source in package search dir.
* Revert syzkaller change, track bug in #3639
|
| |
|
|
| |
(fixes #2148). (#3602)
|
| | |
|
| |
|
|
|
| |
* Documentation update
* Abhishek comments
|
| | |
|
| |
|
|
|
|
| |
accepting only HTTPS connections since approx 14th March.
This allows the builds for guetzli, libjpeg-turbo,
libtiff and libvips to succeed again.
|
| |
|
| |
Just fixing a few spelling mistakes and added some features to the description.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [presubmit] Enforce language attribute in projectt.yaml to be always set.
* Update documentation, better presubmit check, new project template.
* add docstring to templates.py
* Add example values in the project.yaml template and remove python value for now
* Add "project: c++" to 256 projects
* format
* Add labels and selective_unpack sections to the presubmit check
* fix incorrect auto_ccs format in three projects
* fix nss emails after rebase
|
| |
|
|
| |
#3382).
|
| |
|
|
|
|
|
|
| |
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.4 to 1.10.8.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md)
- [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.10.4...v1.10.8)
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
Small change to example file to reflect the current action state.
|
| |
|
| |
Adds functionality to check if a crash exists in the most recent OSS-Fuzz build. This is necessary to determine if a crash was introduced in the current pull request or existed in the project already. Crashes that are surfaced to the user will be both reproducible and novel to the OSS-Fuzz project.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* CIFuzz documentation
* Maxs comments
* Jonathan comments
* Jonathan comments pt.2
* Adding images
* Maxs comments pt.2
* Image spacing
* Maxs comments pt.3
* Jonathan comments
|
| |
|
|
|
|
|
|
|
|
| |
* [infra] Introduce "language" attribute in the project.yaml (#3297).
* follow up
* enable the attribute for more projects
* trailing newline
|
| |
|
|
|
|
|
|
| |
* [docs] Update the main docs page to mention fuzzing docs.
* Add an FAQ entry too
* update the main readme and move the faq question up
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
* [docs] Add "Integrating a Go project" documentation page (#2714).
* rephrase go-fuzz mode description
|
| | |
|
| |
|
|
|
|
|
|
| |
* [Docs]: Copy edit Advanced Topics section.
* Minor tweaks addressing Max's comments.
* Add context for Code Coverage
|
| |
|
|
|
|
|
|
|
|
| |
* [docs] Document shiny new badge in the docs
Use monorail project link instead of build logs
Monorail link has advantage of showing previously found bugs.
It also shows any build failures (though the issue may be hard to find in long-lasting build failures).
The link sorts by date a bug was opened, thus some verified bugs will be shown before more recently opened ones.
|
| |
|
|
|
|
|
|
|
|
| |
* [docs][infra] Add build support for FuzzedDataProvider.
* address review comment
* document the new FDP location
* remove redundant new line
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
* Add documentation for vendor_ccs.
* Address review comments.
|
Abhishek Arya
Max Moroz
devtty1er
Shivam7-1
Evgeny Vereshchagin
Alex Crichton
Zhicheng Cai
jonathanmetzman
Jonathan Metzman
Leo Neat
Robert Löhning
Lovell Fuller
dependabot[bot]
Leo Neat
Oliver Chang
kplybon
Ammar Askar