test-pipeline/orthrus

Issues

• Why [+] Configuring... failed. Do Create instrumented binaries run under source package files?

  #19 opened 2 years ago by blu3sh0rk
  0

• missing --coverage in gcc_coverage build environment

  #18 opened 5 years ago by zjuchenyuan
  0

• Python 3 support

  #17 opened 7 years ago by XVilka
  0

• Refactor code in commands into separate files

  #16 opened 7 years ago by bshastry
  0

• [Show] Expose seeds and qemu in orthrus show

  #15 opened 7 years ago by bshastry
  0

• [Add/Start/Stop] Implement support for afl fuzz in QEMU mode

  #14 opened 7 years ago by bshastry
  0

• [Create] Implement create feature for binary only fuzzing

  #13 opened 7 years ago by bshastry
  0

• [Add] Fold add options into jobconf

  #12 opened 7 years ago by bshastry
  0

• Workaround for afl-utils 'interactive' bug

  #11 opened 7 years ago by bshastry
  0

• Standardize regen for triage, spectrum, and runtime

  #10 opened 7 years ago by bshastry
  0

• Archive runtime results if it exists

  #7 opened 8 years ago by bshastry
  0

• In A/B test mode with corpus minimization, start both fuzzers almost simultaneously

  #3 opened 8 years ago by bshastry
  0

• Archive binaries instead of prompting for a destroy

  #4 opened 8 years ago by bshastry
  0

• Fail elegantly when AFL_HARDEN=1 poses a compilation issue

  #2 opened 8 years ago by bshastry
  0

• Implement a create option for ASAN blacklists

  #5 opened 8 years ago by bshastry
  0

• Bug: Stopping job in ASAN only mode does not terminate fuzzing sessions

  #9 opened 8 years ago by bshastry
  0

• Extend runtime and spectrum for a/b tests

  #8 opened 8 years ago by bshastry
  0

• Implement afl dict auto create during create and use during add job

  #6 opened 8 years ago by bshastry
  0

• orthrus create failed for libpcap

  #1 opened 8 years ago by thelumberjhack
  7