Domovská stránka Prehľadávať Pomoc
Prihlásiť sa
opc-ua
/
open62541
Pridať medzi pozorované 2
Hviezda 0
Fork 0
Súbory Issues 0 Pull requesty 0 Wiki
Strom: 0fa0a0c767
Branche Tagy
open62541
/
tests
/
fuzz
Stefan Profanter 7a58b4fd45 Add generated corpus 7 rokov pred
..
fuzz_binary_message_corpus 7a58b4fd45 Add generated corpus 7 rokov pred
CMakeLists.txt 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 rokov pred
README.md 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 rokov pred
binary.dict 1271ae3417 Better align fuzzing test with real server execution 7 rokov pred
corpus_generator.c 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 rokov pred
fuzz_binary_decode.cc e110f93c36 Add fuzzing of extension object and variant 7 rokov pred
fuzz_binary_message.cc cd3020946e Cleanup server callbacks 7 rokov pred
fuzz_binary_message.options 39059ba3e0 First test for fuzzing 7 rokov pred
generate_corpus.sh 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 rokov pred
oss-fuzz-copy.sh d93bfe31c2 Do not zip corpus directory itself 7 rokov pred
ua_debug_dump_pkgs_file.c 32fc345337 Add fuzz corpus generator from unit tests and integrate into CI 7 rokov pred

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.