Mirrors
/
monero
mirror of https://github.com/monero-project/monero.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
monero/tests/fuzz/CMakeLists.txt

231 lines
6.6 KiB
CMake
Raw Normal View History

Copyright: Update to 2023 Co-authored-by: plowsof <plowsof@protonmail.com> extra files
2023-01-02 08:12:39 -07:00
# Copyright (c) 2014-2023, The Monero Project
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
#
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without modification, are
# permitted provided that the following conditions are met:
#
# 1. Redistributions of source code must retain the above copyright notice, this list of
# conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above copyright notice, this list
# of conditions and the following disclaimer in the documentation and/or other
# materials provided with the distribution.
#
# 3. Neither the name of the copyright holder nor the names of its contributors may be
# used to endorse or promote products derived from this software without specific
# prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
# EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
# THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
# STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(block_fuzz_tests block.cpp fuzzer.cpp)
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
target_link_libraries(block_fuzz_tests
PRIVATE
cryptonote_core
p2p
epee
Code modifications to integrate Ledger HW device into monero-wallet-cli. The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device.
2018-02-20 09:01:27 -07:00
device
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
set_property(TARGET block_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(transaction_fuzz_tests transaction.cpp fuzzer.cpp)
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
target_link_libraries(transaction_fuzz_tests
PRIVATE
cryptonote_core
p2p
epee
Code modifications to integrate Ledger HW device into monero-wallet-cli. The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device.
2018-02-20 09:01:27 -07:00
device
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
set_property(TARGET transaction_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(signature_fuzz_tests signature.cpp fuzzer.cpp)
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
target_link_libraries(signature_fuzz_tests
PRIVATE
wallet
cryptonote_core
p2p
epee
Code modifications to integrate Ledger HW device into monero-wallet-cli. The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device.
2018-02-20 09:01:27 -07:00
device
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
set_property(TARGET signature_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(cold-outputs_fuzz_tests cold-outputs.cpp fuzzer.cpp)
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
target_link_libraries(cold-outputs_fuzz_tests
PRIVATE
wallet
cryptonote_core
p2p
epee
Code modifications to integrate Ledger HW device into monero-wallet-cli. The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device.
2018-02-20 09:01:27 -07:00
device
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
set_property(TARGET cold-outputs_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(cold-transaction_fuzz_tests cold-transaction.cpp fuzzer.cpp)
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
target_link_libraries(cold-transaction_fuzz_tests
PRIVATE
wallet
cryptonote_core
p2p
epee
Code modifications to integrate Ledger HW device into monero-wallet-cli. The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device.
2018-02-20 09:01:27 -07:00
device
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
Add fuzz testing using american fuzzy lop Existing tests: block, transaction, signature, cold outputs, cold transaction. Data for these is in tests/data/fuzz. A convenience shell script is in contrib/fuzz_testing/fuzz.sh, eg: contrib/fuzz_testing/fuzz.sh signature The fuzzer will run indefinitely, ^C to stop. Fuzzing is currently supported for GCC only. I can't get CLANG to build Monero here as it dies on some system headers, so if someone wants to make it work on both, that'd be great. In particular, the __AFL_LOOP construct should be made to work so that a given run can fuzz multiple inputs, as the C++ load time is substantial.
2017-06-24 05:38:41 -06:00
set_property(TARGET cold-transaction_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(load-from-binary_fuzz_tests load_from_binary.cpp fuzzer.cpp)
add load_from_binary/load_from_json fuzzers
2017-12-09 16:04:49 -07:00
target_link_libraries(load-from-binary_fuzz_tests
PRIVATE
common
epee
${Boost_PROGRAM_OPTIONS_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
add load_from_binary/load_from_json fuzzers
2017-12-09 16:04:49 -07:00
set_property(TARGET load-from-binary_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(load-from-json_fuzz_tests load_from_json.cpp fuzzer.cpp)
add load_from_binary/load_from_json fuzzers
2017-12-09 16:04:49 -07:00
target_link_libraries(load-from-json_fuzz_tests
PRIVATE
common
epee
${Boost_PROGRAM_OPTIONS_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
add load_from_binary/load_from_json fuzzers
2017-12-09 16:04:49 -07:00
set_property(TARGET load-from-json_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(base58_fuzz_tests base58.cpp fuzzer.cpp)
tests: add base58 fuzz test
2017-12-10 08:52:24 -07:00
target_link_libraries(base58_fuzz_tests
PRIVATE
common
epee
${Boost_PROGRAM_OPTIONS_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
tests: add base58 fuzz test
2017-12-10 08:52:24 -07:00
set_property(TARGET base58_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(parse-url_fuzz_tests parse_url.cpp fuzzer.cpp)
add parse_url fuzz test
2017-12-10 13:17:16 -07:00
target_link_libraries(parse-url_fuzz_tests
PRIVATE
epee
${Boost_REGEX_LIBRARY}
${Boost_PROGRAM_OPTIONS_LIBRARY}
${Boost_SYSTEM_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
add parse_url fuzz test
2017-12-10 13:17:16 -07:00
set_property(TARGET parse-url_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(http-client_fuzz_tests http-client.cpp fuzzer.cpp)
tests: add http client fuzz test
2017-12-11 02:33:01 -07:00
target_link_libraries(http-client_fuzz_tests
PRIVATE
epee
${Boost_THREAD_LIBRARY}
Tests: Fix building of two fuzz tests on Windows
2018-01-28 06:51:02 -07:00
${Boost_CHRONO_LIBRARY}
tests: add http client fuzz test
2017-12-11 02:33:01 -07:00
${Boost_REGEX_LIBRARY}
${Boost_PROGRAM_OPTIONS_LIBRARY}
${Boost_SYSTEM_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
tests: add http client fuzz test
2017-12-11 02:33:01 -07:00
set_property(TARGET http-client_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(levin_fuzz_tests levin.cpp fuzzer.cpp)
tests: add levin fuzz test
2017-12-11 11:32:40 -07:00
target_link_libraries(levin_fuzz_tests
PRIVATE
common
epee
${Boost_THREAD_LIBRARY}
Tests: Fix building of two fuzz tests on Windows
2018-01-28 06:51:02 -07:00
${Boost_CHRONO_LIBRARY}
tests: add levin fuzz test
2017-12-11 11:32:40 -07:00
${Boost_REGEX_LIBRARY}
${Boost_PROGRAM_OPTIONS_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
tests: add levin fuzz test
2017-12-11 11:32:40 -07:00
set_property(TARGET levin_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(bulletproof_fuzz_tests bulletproof.cpp fuzzer.cpp)
fuzz_tests: add a bulletproof fuzz test
2018-07-27 10:00:48 -06:00
target_link_libraries(bulletproof_fuzz_tests
PRIVATE
common
epee
${Boost_THREAD_LIBRARY}
${Boost_CHRONO_LIBRARY}
${Boost_REGEX_LIBRARY}
${Boost_PROGRAM_OPTIONS_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
fuzz_tests: refactor and add OSS-Fuzz compatibility
2020-05-15 11:17:24 -06:00
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
fuzz_tests: add a bulletproof fuzz test
2018-07-27 10:00:48 -06:00
set_property(TARGET bulletproof_fuzz_tests
PROPERTY
FOLDER "tests")
Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-10-26 13:53:21 -06:00
monero_add_minimal_executable(tx-extra_fuzz_tests tx-extra.cpp fuzzer.cpp)
fuzz_tests: add a tx extra fuzz test
2020-05-16 05:43:45 -06:00
target_link_libraries(tx-extra_fuzz_tests
PRIVATE
cryptonote_basic
common
epee
${Boost_THREAD_LIBRARY}
${Boost_CHRONO_LIBRARY}
${Boost_REGEX_LIBRARY}
${Boost_PROGRAM_OPTIONS_LIBRARY}
${Boost_SYSTEM_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})
set_property(TARGET tx-extra_fuzz_tests
PROPERTY
FOLDER "tests")
fuzz_tests: add a test for utf8canonical
2020-12-14 07:25:44 -07:00
monero_add_minimal_executable(utf8_fuzz_tests utf8.cpp fuzzer.cpp)
target_link_libraries(utf8_fuzz_tests
PRIVATE
common
epee
${Boost_THREAD_LIBRARY}
${Boost_CHRONO_LIBRARY}
${CMAKE_THREAD_LIBS_INIT}
${EXTRA_LIBRARIES}
$ENV{LIB_FUZZING_ENGINE})