Julius Pfrommer
746ad7ede8
New Subscriptions and MonitoredItems Client API
|
6 years ago | |
|---|---|---|
| .. | ||
| fuzz_binary_message_corpus | 7 years ago | |
| CMakeLists.txt | 6 years ago | |
| README.md | 7 years ago | |
| binary.dict | 7 years ago | |
| corpus_generator.c | 6 years ago | |
| fuzz_binary_decode.cc | 7 years ago | |
| fuzz_binary_message.cc | 6 years ago | |
| fuzz_binary_message.options | 7 years ago | |
| generate_corpus.sh | 6 years ago | |
| oss-fuzz-copy.sh | 7 years ago | |
| ua_debug_dump_pkgs_file.c | 7 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.
The script will create two directories:
open62541/build_fuzzandopen62541/build_corpus. Make sure that these directories are not existing or do not contain any important data.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.
- 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.