Module libafl::inputs

Inputs are the actual contents sent to a target for each exeuction.

Re-exports

• pub use bytes::BytesInput;
• pub use encoded::*;
• pub use gramatron::*;
• pub use generalized::*;
• pub use multi::*;
• pub use nautilus::*;

Modules

• bytes
  The BytesInput is the “normal” input, a map of bytes, that can be sent directly to the client (As opposed to other, more abstract, inputs, like an Grammar-Based AST Input)
• encoded
  The EncodedInput is the “normal” input, a map of codes, that can be sent directly to the client (As opposed to other, more abstract, inputs, like an Grammar-Based AST Input) See also the paper on token-level fuzzing
• generalized
  The GeneralizedInput is an input that ca be generalized to represent a rule, used by Grimoire
• gramatron
  The gramatron grammar fuzzer
• multi
  Definitions for inputs which have multiple distinct subcomponents.
• nautilus
  Input for the Nautilus grammar fuzzer methods

Structs

• ClosureInputConverter
  InputConverter that uses a closure to convert
• NopInput
  An input for tests, mainly. There is no real use much else.
• NopInputConverter
  Basic InputConverter with just one type that is not converting

Traits

• HasBytesVec
  Contains an internal bytes Vector
• HasTargetBytes
  Can be represented with a vector of bytes. This representation is not necessarily deserializable. Instead, it can be used as bytes input for a target
• Input
  An input for the target
• InputConverter
  Convert between two input types with a state
• UsesInput
  Defines the input type shared across traits of the type. Needed for consistency across HasCorpus/HasSolutions and friends.