mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 18:11:28 +01:00
Code Issues Projects Releases Wiki Activity
d60077a8d9
core-lightning/tests/fuzz/Makefile

71 lines
2.0 KiB
Makefile
Raw Normal View History

build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
LIBFUZZ_SRC := tests/fuzz/libfuzz.c
LIBFUZZ_HEADERS := $(LIBFUZZ_SRC:.c=.h)
LIBFUZZ_OBJS := $(LIBFUZZ_SRC:.c=.o)
fuzz: add handshake act 1 target The fuzz target uses static keys with a fuzzer-generated Act 1 packet.
2023-06-08 18:24:11 +02:00
tests/fuzz/fuzz-connectd-handshake-act*.o: tests/fuzz/connectd_handshake.h
fuzz: add ripemd160 target The target fuzzes CCAN's implementation of ripemd160 and compares the hash results against OpenSSL's implementation.
2023-06-27 23:32:11 +02:00
tests/fuzz/fuzz-ripemd160: LDLIBS += -lcrypto
fuzz: add sha256 target The target fuzzes CCAN's implementation of sha256 and compares the hash results against OpenSSL's implementation.
2023-06-27 23:34:56 +02:00
tests/fuzz/fuzz-sha256: LDLIBS += -lcrypto
fuzz: target for accept_channel Fuzz the decoding and encoding of accept_channel. We create a wire.h header to share code with future targets.
2023-08-21 21:42:54 +02:00
tests/fuzz/fuzz-wire-*.o: tests/fuzz/wire.h
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
FUZZ_TARGETS_SRC := $(wildcard tests/fuzz/fuzz-*.c)
FUZZ_TARGETS_OBJS := $(FUZZ_TARGETS_SRC:.c=.o)
FUZZ_TARGETS_BIN := $(FUZZ_TARGETS_SRC:.c=)
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
FUZZ_COMMON_OBJS := \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
common/amount.o \
common/addr.o \
fuzz: make it build again. How did this pass CI? I saw this break in my PR, but it's (long) broken in master. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-10-13 05:42:42 +02:00
common/autodata.o \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
common/base32.o \
fuzz: add a target for base32/64 encoding Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-10 18:19:58 +02:00
common/base64.o \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
common/bech32.o \
fuzz: add a fuzz target for common/bip32 Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-23 12:13:46 +02:00
common/bip32.o \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
common/bigsize.o \
fuzz: make it build again. How did this pass CI? I saw this break in my PR, but it's (long) broken in master. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-10-13 05:42:42 +02:00
common/blockheight_states.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/channel_config.o \
fuzz: add a fuzz target for the close tx Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-23 17:14:17 +02:00
common/close_tx.o \
fuzz: fix fuzzing compilation. It had bitrotted. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-07-25 08:59:09 +02:00
common/configdir.o \
lightningd: switch parsing to common/configvar Now we wire in the code which gathers configvars and parses from there; lightningd keeps the array of configuration variables for future use. Note that lightning-cli also needs to read the config, but it has its own options (including short ones!) and doesn't want to use this configvar mechanism, so we have a different API for that now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-06-02 04:35:51 +02:00
common/configvar.o \
fuzz: add a fuzz target for channel_id derivation Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-23 13:56:36 +02:00
common/channel_id.o \
fuzz: make it build again. How did this pass CI? I saw this break in my PR, but it's (long) broken in master. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-10-13 05:42:42 +02:00
common/channel_type.o \
fuzz: test message encryption and decryption Add a fuzz test for BOLT 8 message encryption and decryption. The fuzz test is based on the unit test at common/test/run-cryptomsg.c and uses a static initial state with fuzzer-generated messages to encrypt or decrypt.
2023-06-07 19:02:16 +02:00
common/cryptomsg.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/daemon.o \
common/daemon_conn.o \
common/derive_basepoints.o \
fuzz: add a fuzz target for common/descriptor_checksum A small one just to check that we don't crash nor go out of bounds! Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-30 15:29:07 +01:00
common/descriptor_checksum.o \
fuzz: make it build again. How did this pass CI? I saw this break in my PR, but it's (long) broken in master. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-10-13 05:42:42 +02:00
common/features.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/fee_states.o \
tests/fuzz: add a fuzz target for hsm_encryption Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2021-01-03 21:29:18 +01:00
common/hsm_encryption.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/htlc_state.o \
fuzz: add a fuzz target for the close tx Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-23 17:14:17 +02:00
common/permute_tx.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/initial_channel.o \
common/initial_commit_tx.o \
common/key_derive.o \
common/keyset.o \
common/msg_queue.o \
common/memleak.o \
common/node_id.o \
fuzz: fix fuzzing compilation. It had bitrotted. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-07-25 08:59:09 +02:00
common/psbt_keypath.o \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
common/wireaddr.o \
fuzz: add a fuzz target for the close tx Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-23 17:14:17 +02:00
common/setup.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/status.o \
common/status_wire.o \
common/status_wiregen.o \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
common/type_to_string.o \
fuzz: add a fuzz target for amounts parsing Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-08 16:28:56 +02:00
common/utils.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
common/version.o \
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
wire/fromwire.o \
wire/onion_wiregen.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
wire/peer_wire.o \
build: don't generate experimental variants of wire files. We no longer have any experimental-only wire definitions. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-05-22 02:51:44 +02:00
wire/peer_wiregen.o \
fuzz: make it build again. How did this pass CI? I saw this break in my PR, but it's (long) broken in master. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-10-13 05:42:42 +02:00
wire/channel_type_wiregen.o \
libfuzz: add a NULL-termination in to_string It's more useful if we actually want to use the output as, well, a string.. Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2021-01-03 21:21:36 +01:00
wire/tlvstream.o \
fuzz: add a fuzz target for initial_channel Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-10-14 17:17:57 +02:00
wire/towire.o \
wire/wire_io.o \
wire/wire_sync.o
fuzz: add a fuzz target for amounts parsing Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-08 16:28:56 +02:00
$(FUZZ_TARGETS_OBJS): $(COMMON_HEADERS) $(WIRE_HEADERS) $(COMMON_SRC)
$(FUZZ_TARGETS_BIN): $(LIBFUZZ_OBJS) $(FUZZ_COMMON_OBJS) $(BITCOIN_OBJS)
build: introduce a fuzzing mode This adds a new configuration, --enable-fuzzing (which is more than welcome to be coupled with --enable-address-sanitizer), to pass the fuzzer sanitizer argument when compiling objects. This allows libfuzzer to actually be able "to fuzz" by detecting coverage and be smart when mutating inputs. As libfuzzer brings its own ~~fees~~ main(), we compile objects with fsanitize=fuzzer-no-link, and special-case the linkage of the fuzz targets. A "lib" is added to abstract out the interface to the fuzzing tool used. This allow us to use the same targets to fuzz using AFL, hongfuzz or w/e by adding their entrypoints into libfuzz. (h/t to practicalswift who introduced this for bitcoin-core, which i mimiced) Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2020-09-07 17:32:19 +02:00
ALL_C_SOURCES += $(FUZZ_TARGETS_SRC) $(LIBFUZZ_SRC)
ALL_FUZZ_TARGETS += $(FUZZ_TARGETS_BIN)
Reference in New Issue Copy Permalink