Etusivu Tutki Apua
Kirjaudu sisään
opc-ua
/
open62541
Tarkkaile 2
Äänestä 0
Fork 0
Tiedostot Ongelmat 0 Pull-pyynnöt 0 Wiki
Puu: 6c82b082c8
Branchit Tagit
open62541
/
tests
/
fuzz
Stefan Profanter 660165267e Fix oss fuzz copy 7 vuotta sitten
..
fuzz_binary_message_corpus 7a58b4fd45 Add generated corpus 7 vuotta sitten
CMakeLists.txt 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 vuotta sitten
README.md 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 vuotta sitten
binary.dict 1271ae3417 Better align fuzzing test with real server execution 7 vuotta sitten
corpus_generator.c d86e04a925 clean some gcc7 errors in the corpus generation 7 vuotta sitten
fuzz_binary_decode.cc e110f93c36 Add fuzzing of extension object and variant 7 vuotta sitten
fuzz_binary_message.cc 9313d4ee0d fix a unasigned memory problem in the fuzzer 7 vuotta sitten
fuzz_binary_message.options 39059ba3e0 First test for fuzzing 7 vuotta sitten
generate_corpus.sh 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 vuotta sitten
oss-fuzz-copy.sh 660165267e Fix oss fuzz copy 7 vuotta sitten
ua_debug_dump_pkgs_file.c d86e04a925 clean some gcc7 errors in the corpus generation 7 vuotta sitten

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.