Stefan Profanter 23f57fc4c0 Update corpus пре 6 година
..
fuzz_binary_message_corpus 23f57fc4c0 Update corpus пре 6 година
CMakeLists.txt bc8ca555b0 remove sha1 function пре 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 пре 7 година
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 da64add5c0 client basic 256sha256 / server sample / tests / various fixes (#1691) пре 6 година

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.