Начало Каталог Помощ
Вход
thomas
/
open62541
Наблюдаван 1
Харесван 0
Разклонения 0
Файлове Задачи 0 Заявки за сливане 0 Уики
ИН на ревизия: 3af3d9d969
Клонове Маркери
open62541
/
tests
/
fuzz
StalderT 65db398dcb add client to dataChangeHandler преди 6 години
..
fuzz_binary_message_corpus 0de0660976 Correctly handle corpus generator error and add additional corpus преди 6 години
CMakeLists.txt adf793b2ef Implement SecurityPolicy#Basic128Rsa15 with mbedTLS преди 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 65db398dcb add client to dataChangeHandler преди 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 0de0660976 Correctly handle corpus generator error and add additional corpus преди 6 години
oss-fuzz-copy.sh 660165267e Fix oss fuzz copy преди 6 години
ua_debug_dump_pkgs_file.c d86e04a925 clean some gcc7 errors in the corpus generation преди 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.