Skip to content

fix some typos in first two sections#25

Open
shiheyuan wants to merge 1 commit into
hardenedlinux:masterfrom
shiheyuan:patch-1
Open

fix some typos in first two sections#25
shiheyuan wants to merge 1 commit into
hardenedlinux:masterfrom
shiheyuan:patch-1

Conversation

@shiheyuan
Copy link
Copy Markdown

No description provided.

@Bins94 Bins94 closed this Mar 17, 2020
@Bins94 Bins94 reopened this Mar 17, 2020
Comment thread survey.md
## Brief
## Overview

This document will introduce some features or design of customizing fuzzer. Firstly, most of fuzzer implemented its own Genetic Algorithm( GA). Some features can be classified to one of GA component. For example, the optimizing of generate, mutate and crossover. Other features, such as special feedback or satifying deep nested condition, is strongly depend on what project you fuzz, although these problem is very common in real-world project.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remain the format of "( ***)".

Comment thread survey.md
Comment on lines +10 to 11
In most fuzzers, GA is the engine of evolving testcase. For different purposes, the design of GA's components can be quite different.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep two empty line before title and one empty line after.

Comment thread survey.md
3. Manually write manner: hard-code some special inputs or enum inputs.( Syzkaller)
4. Extract input from real-world program( Moonshine).
In evolutionary programming, if mutation and generating only base on random inputs, that fuzzer will perform badly. Useful information help to reduce the search space of evolving the testcase you want. Generally, these following information can benefit mutating or generating:
1. symbolic execution: static analysis target, deriver which inputs are useful. (KLEE)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

static analyse( should be a vt.) targeted project, right?

Comment thread survey.md
3. Manually write manner: hard-code some special inputs or enum inputs.( Syzkaller)
4. Extract input from real-world program( Moonshine).
In evolutionary programming, if mutation and generating only base on random inputs, that fuzzer will perform badly. Useful information help to reduce the search space of evolving the testcase you want. Generally, these following information can benefit mutating or generating:
1. symbolic execution: static analysis target, deriver which inputs are useful. (KLEE)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep all list like:

  1. symbolic execution: static analysis target, deriver which inputs are useful.( KLEE)
    "deriver" should be "derive"

Comment thread survey.md
#### state

1. Symbolic execution: static analyse call-stack input, weight them base on its CFG
1. Symbolic execution: static analysis call-stack input, weight them base on its CFG
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

static analyse( should be vt.) call-stack inputs, right?

Comment thread survey.md
## Brief
## Overview

This document will introduce some features or design of customizing fuzzer. Firstly, most of fuzzer implemented its own Genetic Algorithm( GA). Some features can be classified to one of GA component. For example, the optimizing of generate, mutate and crossover. Other features, such as special feedback or satifying deep nested condition, is strongly depend on what project you fuzz, although these problem is very common in real-world project.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be "these problems are very common in real-world projects.", right?

@Bins94
Copy link
Copy Markdown
Contributor

Bins94 commented Mar 19, 2020

Hi, @shiheyuan , could you modify it and send again? Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants