Comments (7)
Should this be documented in the build pipeline doc or the libfuzzer_and_afl doc?
from clusterfuzz.
I think some part of it must be in the build pipeline, at least the naming format and the requirement to archive that into the same dir with the fuzzing binary -- just because it totally belongs to the build system. More detail can be added in libfuzzer_and_afl doc, I guess. Some notes about how important those things are?
from clusterfuzz.
just because it totally belongs to the build system.
I don't really see why, dictionary and seed corpus work just as well with custom builds.
I think it would be best for build pipeline to be solely about continuous building rather than about all things about builds (which is why I cover building targets for AFL and libFuzzer in that doc).
from clusterfuzz.
Good point regarding custom builds! Maybe we should have some generic sentence in the build pipeline then, like "Make sure to include all important build artifacts into the archive (e.g. dictionaries or seed corpora [link], some other example [link], etc)"
from clusterfuzz.
I just want to make sure people remember this stuff when they write a script / build rule for generating a build archive.
from clusterfuzz.
OK sgtm.
from clusterfuzz.
#96 does this.
from clusterfuzz.
Related Issues (20)
- Figure out how regression task used trusted code HOT 2
- Fix permissions issue with global leak blacklist
- Fix privileged operation in variant
- Handle permission denied error in minimize
- Fix privileged operation: Downloading custom binaries
- Remove privileged operation from minimize task
- Handle insufficient privileges in progression task
- Transition from Container Registry HOT 1
- Fix fuzztest detection HOT 1
- Get rid of "Failed to parse logcat line: E/" HOT 1
- Handle target deletion in split builds
- Allow job weights to be set manually HOT 5
- corpus_pruning task needs privileges HOT 3
- Ensure heartbeat doesnt run on batch instances HOT 1
- Investigate windows instances that aren't logging
- Fix Android ability to launch Cuttlefish Images
- Automatic closure date is in the past HOT 3
- Allow custom builds in nonprivileged execution HOT 1
- Ensure that impact tasks aren't run on non-chrome projects
- Fix issues with zero size thread pools. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from clusterfuzz.