Strona główna Odkrywaj Pomoc
Zaloguj się
thomas
/
open62541
Obserwuj 1
Polub 0
Forkuj 0
Pliki Problemy 0 Oczekujące zmiany 0 Wiki
Drzewo: 0c3423036d
Gałęzie Tagi
open62541
/
tests
/
fuzz
Stefan Profanter a0d6e2b166 Further adaption to architecture folder 6 lat temu
..
fuzz_binary_message_corpus 23f57fc4c0 Update corpus 6 lat temu
CMakeLists.txt a0d6e2b166 Further adaption to architecture folder 6 lat temu
README.md 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 lat temu
binary.dict 1271ae3417 Better align fuzzing test with real server execution 7 lat temu
corpus_generator.c 4381a3a85b Remove deprecated methods from generate corpus 6 lat temu
fuzz_binary_decode.cc e110f93c36 Add fuzzing of extension object and variant 7 lat temu
fuzz_binary_message.cc 448e4e100c Additional error checking if initialization fails 6 lat temu
fuzz_binary_message.options 39059ba3e0 First test for fuzzing 7 lat temu
generate_corpus.sh 108fcddbba Split architecture related functions to separated folder 6 lat temu
oss-fuzz-copy.sh 660165267e Fix oss fuzz copy 7 lat temu
ua_debug_dump_pkgs_file.c da64add5c0 client basic 256sha256 / server sample / tests / various fixes (#1691) 6 lat temu

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.