mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-12-29 10:04:41 +01:00
Code Issues Projects Releases Wiki Activity
0d94530f13
core-lightning/tests/fuzz/Makefile

65 lines
1.7 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_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: 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: 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 \
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/json.o \
common/json_stream.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/key_derive.o \
common/keyset.o \
common/msg_queue.o \
common/memleak.o \
common/node_id.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 \
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/peer$(EXP)_wiregen.o \
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