Mark Giraud 37e8654da8 SecurityPolicy Interface change (#1613) лет назад: 6
..
fuzz_binary_message_corpus 0de0660976 Correctly handle corpus generator error and add additional corpus лет назад: 7
CMakeLists.txt 37e8654da8 SecurityPolicy Interface change (#1613) лет назад: 6
README.md 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI лет назад: 7
binary.dict 1271ae3417 Better align fuzzing test with real server execution лет назад: 7
corpus_generator.c 746ad7ede8 New Subscriptions and MonitoredItems Client API лет назад: 6
fuzz_binary_decode.cc e110f93c36 Add fuzzing of extension object and variant лет назад: 7
fuzz_binary_message.cc 448e4e100c Additional error checking if initialization fails лет назад: 6
fuzz_binary_message.options 39059ba3e0 First test for fuzzing лет назад: 7
generate_corpus.sh 2be85c4381 Add mbedtls installation лет назад: 6
oss-fuzz-copy.sh 660165267e Fix oss fuzz copy лет назад: 7
ua_debug_dump_pkgs_file.c d86e04a925 clean some gcc7 errors in the corpus generation лет назад: 7

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.