Stefan Profanter 4381a3a85b Remove deprecated methods from generate 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	6 年之前
binary.dict	1271ae3417 Better align fuzzing test with real server execution	6 年之前
corpus_generator.c	4381a3a85b Remove deprecated methods from generate corpus	6 年之前
fuzz_binary_decode.cc	e110f93c36 Add fuzzing of extension object and variant	6 年之前
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	6 年之前
ua_debug_dump_pkgs_file.c	da64add5c0 client basic 256sha256 / server sample / tests / various fixes (#1691)	6 年之前

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_fuzz and open62541/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.

README.md

I Can haz fuzz

Status

Update the corpus