Julius Pfrommer 49e0a0bb1e Types: Add UA_DataTypeArray as a linked list for client/server 6 years ago
..
fuzz_binary_message_corpus 23f57fc4c0 Update corpus 6 years ago
CMakeLists.txt a0d6e2b166 Further adaption to architecture folder 6 years ago
README.md 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 years ago
binary.dict 1271ae3417 Better align fuzzing test with real server execution 7 years ago
corpus_generator.c 4381a3a85b Remove deprecated methods from generate corpus 6 years ago
fuzz_binary_decode.cc 49e0a0bb1e Types: Add UA_DataTypeArray as a linked list for client/server 6 years ago
fuzz_binary_message.cc 448e4e100c Additional error checking if initialization fails 6 years ago
fuzz_binary_message.options 39059ba3e0 First test for fuzzing 7 years ago
generate_corpus.sh 6d44b199ef Use Dockerized travis builds and add gcc8 build to matrix 6 years ago
oss-fuzz-copy.sh 660165267e Fix oss fuzz copy 7 years ago
ua_debug_dump_pkgs_file.c cf6e89d6b7 Fix #1930 6 years ago

README.md

I Can haz fuzz

open62541 is continuously tested with the awesome oss-fuzz project from Google: https://github.com/google/oss-fuzz

Currently tested is processing of binary messages and encoding/decoding of binary encoded data.

Status

Update the corpus

To update the current corpus used for fuzzing you need to follow these steps. It will execute all the unit tests, dump the received data packages to a directory and then update and merge the corpus.

  1. The script will create two directories: open62541/build_fuzz and open62541/build_corpus. Make sure that these directories are not existing or do not contain any important data.

  2. Run the generate script:

open62541/tests/fuzz/generate_corpus.sh

This script will build all the unit tests, dump the packages and then merge the current corpus with the new packages.

  1. If there is new coverage with the generated data there will be new files in the directory:

open62541/fuzz/fuzz_binary_message_corpus/generated

Commit the new files and then you can delete the build directories created in step 1.