blob: e1164097841c752c2b5102fb26ab713d8a245446 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
# Fuzzer environment on ClusterFuzz
Your fuzz targets will be run on a [Google Compute Engine](https://cloud.google.com/compute/) VM (Linux) with some security restrictions.
## Runtime Dependencies
You should not make any assumptions on the availability of dependent packages
and libraries in the execution environment. Make sure to statically link any
library dependencies with your fuzz target executable during build time
([example](https://github.com/google/oss-fuzz/blob/master/projects/tor/build.sh#L40)).
All build artifacts needed during fuzz target execution should be inside `$OUT`
directory. Other directories like `$WORK`, `$SRC` OR dependent packages installed
in build.sh will not be available.
You should ensure that the fuzz target works correctly by using `run_fuzzer` command
(see instructions [here](new_project_guide.md#testing-locally)). This command uses
a clean base-runner docker container and not the base-builder docker container
created during build-time.
## argv[0]
You must not modify argv[0]. It is required for certain things to work correctly.
## Current working directory
You should not make any assumptions about the current working directory of your
fuzz target. If you need to load data files, please use `argv[0]` to get the
directory where your fuzz target executable is located.
## File system
Everything except `/tmp` is read-only, including the directory that your fuzz target
executable lives in.
`/dev` is also unavailable.
## Network access
There will be no network interfaces available (not even loopback).
|
