Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
eb488001
Commit
eb488001
authored
Jul 16, 2020
by
Seth Berger
Committed by
Nick Gaskill
Jul 16, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Updated docs to reflect current capabilities
parent
ccf299df
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
3 deletions
+2
-3
doc/user/application_security/coverage_fuzzing/index.md
doc/user/application_security/coverage_fuzzing/index.md
+2
-3
No files found.
doc/user/application_security/coverage_fuzzing/index.md
View file @
eb488001
...
...
@@ -61,14 +61,13 @@ The `gitlab-cov-fuzz` is a command-line tool that runs the instrumented applicat
analyzes the exception information that the fuzzer outputs. It also downloads the
[
corpus
](
#glossary
)
and crash events from previous pipelines automatically. This helps your fuzz targets build on the progress of
previous fuzzing jobs. The parsed crash events and data are written to
`gl-coverage-fuzzing-report.json`
and then displayed in the pipeline and security dashboard
.
`gl-coverage-fuzzing-report.json`
.
### Artifacts
Each fuzzing step outputs these artifacts:
-
`gl-coverage-fuzzing-report.json`
: Parsed by GitLab's backend to show results in the security
dashboard. This file's format may change in future releases.
-
`gl-coverage-fuzzing-report.json`
: This file's format may change in future releases.
-
`artifacts.zip`
: This file contains two directories:
-
`corpus`
: Holds all test cases generated by the current and all previous jobs.
-
`crashes`
: Holds all crash events the current job encountered as well as those not fixed in
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment