1. 22 Jan, 2020 2 commits
  2. 20 Jan, 2020 1 commit
  3. 17 Jan, 2020 11 commits
  4. 15 Jan, 2020 9 commits
  5. 14 Jan, 2020 1 commit
  6. 10 Jan, 2020 7 commits
  7. 03 Jan, 2020 2 commits
  8. 20 Dec, 2019 7 commits
    • Stephen Morris's avatar
      [#640] Minor corrections · 118f505b
      Stephen Morris authored
      1. Update to documentation concerning the running of until tests
         which code is compiled with fuzzing enabled.
      2. Correction of text of fuzzing-related initialization exception.
      118f505b
    • Stephen Morris's avatar
      [#640] Fuzzing-related configure.ac updates · bfdc3fb8
      Stephen Morris authored
      1. The switch to enable fuzzing is now "--enable-fuzzing".
      2. A check is now made to see that the CXX environment variable
         points to an AFL-enabled compiler when the switch is modified.
      bfdc3fb8
    • Stephen Morris's avatar
      [#640] Implement consistent fuzz packet naming · 9ab23e34
      Stephen Morris authored
      The convention is that all packets used in fuzzing have the file extension
      .pkt.  This commit has renamed some packets to match that convention.
      9ab23e34
    • Stephen Morris's avatar
      d05d2163
    • Stephen Morris's avatar
      [#640] Add fuzzing documentation · 297f23fb
      Stephen Morris authored
      Add a doxygen file describing the fuzzing - how to build and
      run it, and a brief description of the changes made to the code.
      297f23fb
    • Stephen Morris's avatar
      [#640] Simplification of fuzzing structure · 08381e67
      Stephen Morris authored
      Instead of using a separate thread to read input from the fuzzer,
      the input is now read in the main thread and transferred to the
      interface on which Kea is expecting it to appear.
      08381e67
    • Stephen Morris's avatar
      [#640] Major refactoring of fuzzing code · 57e98c22
      Stephen Morris authored
      1. Convert to C++ class.
      2. Extend framework to support DHCPv4 fuzzing.
      3. Restrict size of data that can be accepted from AFL. (Kea will
         only accept up to about 64k or data, (set by the size of a UDP
         datagram).  However, AFL can send much larger data packets,
         which may cause problems in synchronization between the two
         threads used to implement fuzzing in Kea.
      57e98c22