High level conclusions

Fuzzers reach 58.46% code coverage.

Fuzzers reach 22.34% of cyclomatic complexity.

Fuzzers reach 23.07% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

500 / 2167

Cyclomatic complexity statically reachable by fuzzers

2862 / 12806

Runtime code coverage of functions

1267 / 2167

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: fuzz_sigimport

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	7	100.%
All colors	7	100

Runtime coverage analysis

Covered functions

464

Functions that are reachable but not covered

0

Reachable functions

7

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/sigimport.c	1

Fuzzer: fuzz_verify_detached

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	10	100.%
All colors	10	100

Runtime coverage analysis

Covered functions

621

Functions that are reachable but not covered

0

Reachable functions

8

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/verify_detached.c	1

Fuzzer: fuzz_keyring_g10

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	1415	73.5%
gold	[1:9]	37	1.92%
yellow	[10:29]	43	2.23%
greenyellow	[30:49]	33	1.71%
lawngreen	50+	396	20.5%
All colors	1924	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
385	1046	rnp::Key::is_primary() const	call site: 01046	__cxa_allocate_exception
264	1432	rnp::SecurityContext::time() const	call site: 01432	__dynamic_cast
195	573	parse_seckey(pgp_key_pkt_t&, sexp::sexp_list_t const*)	call site: 00573	fprintf
153	807	rnp::Key::Key()	call site: 00807	__clang_call_terminate
76	460	parse_protected_seckey(pgp_key_pkt_t&, sexp::sexp_list_t const*, char const*)	call site: 00460	fprintf
63	1823	rnp::Key::refresh_data(rnp::SecurityContext const&)	call site: 01823	fprintf
43	976	rnp::Key::operator=(rnp::Key&&)	call site: 00976	__dynamic_cast
25	1708	rnp::KeyStore::refresh_subkey_grips(rnp::Key&)	call site: 01708	__cxa_begin_catch
15	769	sexp::sexp_list_t::~sexp_list_t()	call site: 00769	__cxa_begin_catch
15	1786	rnp::Key::validate_primary(rnp::KeyStore&)	call site: 01786	__dynamic_cast
13	1767	rnp::Key::validate_primary(rnp::KeyStore&)	call site: 01767
11	1033	rnp::Key::is_subkey() const	call site: 01033	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

377

Functions that are reachable but not covered

649

Reachable functions

1049

Percentage of reachable functions covered

38.13%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/keyring_g10.cpp	1
/src/rnp/src/lib/sec_profile.cpp	8
/src/rnp/src/lib/sec_profile.hpp	3
/src/rnp/src/lib/crypto/rng.cpp	2
/src/rnp/src/lib/types.h	8
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/usr/include/botan-3/botan/system_rng.h	1
/usr/include/botan-3/botan/rng.h	1
/src/rnp/src/lib/crypto/backend_version.cpp	2
/src/rnp/include/rekey/rnp_key_store.h	1
/src/rnp/src/librepgp/stream-common.cpp	16
/src/rnp/src/lib/logging.cpp	1
/src/rnp/src/librekey/key_store_g10.cpp	24
/src/rnp/src/librepgp/stream-common.h	13
/src/rnp/src/lib/../librepgp/stream-key.h	1
/src/rnp/src/librekey/g23_sexp.hpp	4
/src/rnp/src/libsexpp/include/sexpp/ext-key-format.h	6
/src/rnp/src/libsexpp/include/sexpp/sexp.h	29
/src/rnp/src/libsexpp/src/sexp-input.cpp	18
/src/rnp/src/libsexpp/src/sexp-depth-manager.cpp	4
/src/rnp/src/libsexpp/src/ext-key-format.cpp	4
/src/rnp/src/libsexpp/src/sexp-object.cpp	2
/src/rnp/src/libsexpp/src/sexp-error.cpp	2
/src/rnp/src/libsexpp/include/sexpp/sexp-error.h	3
/src/rnp/src/lib/utils.cpp	2
/src/rnp/src/common/str-utils.cpp	1
/src/rnp/src/lib/crypto/dsa.h	5
/src/rnp/src/lib/crypto/mpi.hpp	4
/src/rnp/src/lib/crypto/mpi.cpp	5
/src/rnp/src/lib/key_material.cpp	29
/src/rnp/src/lib/key_material.hpp	9
/src/rnp/src/lib/crypto/mem.cpp	2
/src/rnp/src/lib/crypto/rsa.h	5
/src/rnp/src/lib/crypto/elgamal.h	5
/src/rnp/src/lib/crypto/ec.h	6
/usr/local/bin/../include/c++/v1/stdexcept	1
/src/rnp/src/libsexpp/src/sexp-output.cpp	5
/usr/local/bin/../include/c++/v1/sstream	3
/src/rnp/src/lib/crypto/symmetric_common.cpp	2
/src/rnp/src/lib/crypto/s2k.cpp	3
/src/rnp/src/lib/crypto/hash.cpp	3
/src/rnp/src/lib/crypto/cipher.cpp	2
/src/rnp/src/lib/crypto/cipher_botan.cpp	4
/src/rnp/src/lib/crypto/hash_common.cpp	5
/src/rnp/src/lib/crypto/hash_sha1cd.cpp	2
/src/rnp/src/lib/crypto/hash.hpp	1
/src/rnp/src/lib/crypto/sha1cd/sha1.c	1
/src/rnp/src/librepgp/stream-key.cpp	9
/src/rnp/src/lib/key.hpp	3
/src/rnp/src/lib/fingerprint.cpp	5
/src/rnp/src/lib/rawpacket.hpp	4
/src/rnp/src/lib/signature.hpp	15
/src/rnp/src/lib/fingerprint.hpp	4
/src/rnp/src/lib/key-provider.cpp	8
/src/rnp/src/lib/key-provider.h	3
/src/rnp/src/lib/key.cpp	77
/src/rnp/src/librepgp/stream-packet.cpp	18
/src/rnp/src/lib/rawpacket.cpp	2
/src/rnp/src/lib/utils.h	3
/src/rnp/src/librekey/rnp_key_store.cpp	10
/src/rnp/src/lib/../librepgp/stream-sig.h	1
/src/rnp/src/librepgp/stream-sig.cpp	27
/src/rnp/src/lib/sig_subpacket.hpp	18
/src/rnp/src/lib/crypto/mem.h	1
/src/rnp/src/lib/userid.cpp	3
/src/rnp/src/lib/signature.cpp	4
/src/rnp/src/lib/crypto/signatures.cpp	3
/src/rnp/src/lib/crypto/sm2.cpp	2
/src/rnp/src/lib/crypto/botan_utils.hpp	7
/src/rnp/src/lib/crypto/ec_curves.cpp	1
/src/rnp/src/librepgp/stream-sig.h	1
/src/rnp/src/lib/sig_material.cpp	1
/src/rnp/src/lib/sig_material.hpp	8
/src/rnp/src/lib/crypto/dilithium_exdsa_composite.h	1
/src/rnp/src/lib/crypto/sphincsplus.h	1
/src/rnp/src/lib/sig_subpacket.cpp	1

Fuzzer: fuzz_verify

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	10	100.%
All colors	10	100

Runtime coverage analysis

Covered functions

805

Functions that are reachable but not covered

0

Reachable functions

10

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/verify.c	1

Fuzzer: fuzz_dump

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	10	100.%
All colors	10	100

Runtime coverage analysis

Covered functions

740

Functions that are reachable but not covered

0

Reachable functions

8

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/dump.c	1

Fuzzer: fuzz_keyring

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

2014

Functions that are reachable but not covered

0

Reachable functions

6

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/keyring.c	1

Fuzzer: fuzz_keyimport

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	25	100.%
All colors	25	100

Runtime coverage analysis

Covered functions

2032

Functions that are reachable but not covered

0

Reachable functions

7

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/keyimport.c	1

Fuzzer: fuzz_keyring_kbx

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

2021

Functions that are reachable but not covered

0

Reachable functions

6

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/rnp/src/fuzzing/keyring_kbx.c	1

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name	Functions filename	Arg count	Args	Function depth	hitcount	instr count	bb count	cyclomatic complexity	Reachable functions	Incoming references	total cyclomatic complexity	Unreached complexity
rnp::KeyStore::load(rnp::KeyProviderconst*)	/src/rnp/src/librekey/rnp_key_store.cpp	2	['N/A', 'N/A']	16	0	182	39	4	1439	0	4363	1485
rnp::KeygenParams::generate(rnp::BindingParams&,rnp::Key&,rnp::Key&,rnp::Key&,rnp::Key&,pgp_password_provider_tconst&,rnp::KeyFormat)	/src/rnp/src/lib/keygen.cpp	8	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'int']	15	0	302	76	72	1369	0	4212	889
pgp::DilithiumEccKeyMaterial::generate(rnp::SecurityContext&,pgp::KeyParamsconst&)	/src/rnp/src/lib/key_material.cpp	3	['N/A', 'N/A', 'N/A']	9	0	42	8	4	231	0	439	401
rnp::KeyStore::write()	/src/rnp/src/librekey/rnp_key_store.cpp	1	['N/A']	8	0	297	59	13	200	0	662	392
rnp::KeygenParams::generate(rnp::CertParams&,rnp::Key&,rnp::Key&,rnp::KeyFormat)	/src/rnp/src/lib/keygen.cpp	5	['N/A', 'N/A', 'N/A', 'N/A', 'int']	15	0	237	58	47	1381	0	4139	266
pgp::MlkemEcdhKeyMaterial::generate(rnp::SecurityContext&,pgp::KeyParamsconst&)	/src/rnp/src/lib/key_material.cpp	3	['N/A', 'N/A', 'N/A']	9	0	42	8	4	233	0	438	238
pgp::MlkemEcdhKeyMaterial::decrypt(rnp::SecurityContext&,std::__1::vector >&,pgp::EncMaterialconst&)const	/src/rnp/src/lib/key_material.cpp	4	['N/A', 'N/A', 'N/A', 'N/A']	8	0	44	9	4	195	0	394	211

Implementing fuzzers that target the above functions will improve reachability such that it becomes:

Functions statically reachable by fuzzers

1007 / 2167

Cyclomatic complexity statically reachable by fuzzers

6646 / 12806

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

/src/rnp/src/fuzzing/sigimport.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/src/rnp/src/fuzzing/verify_detached.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/src/rnp/src/fuzzing/keyring_g10.cpp

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['rnp::Key::is_primary() const', 'rnp::SecurityContext::time() const', 'parse_seckey(pgp_key_pkt_t&, sexp::sexp_list_t const*)', 'rnp::Key::Key()', 'parse_protected_seckey(pgp_key_pkt_t&, sexp::sexp_list_t const*, char const*)', 'rnp::Key::refresh_data(rnp::SecurityContext const&)', 'rnp::Key::operator=(rnp::Key&&)', 'rnp::KeyStore::refresh_subkey_grips(rnp::Key&)', 'sexp::sexp_list_t::~sexp_list_t()', 'rnp::Key::validate_primary(rnp::KeyStore&)']

/src/rnp/src/fuzzing/verify.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/src/rnp/src/fuzzing/dump.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/src/rnp/src/fuzzing/keyring.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/src/rnp/src/fuzzing/keyimport.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/src/rnp/src/fuzzing/keyring_kbx.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

This section shows analysis of runtime coverage data.

For futher technical details on how this section is generated, please see the Glossary .

Complex functions with low coverage

Func name	Function total lines	Lines covered at runtime	percentage covered	Reached by fuzzers
Botan::MessageAuthenticationCode::create(std::__1::basic_string_view >,std::__1::basic_string_view >)	44	10	22.72%
rnp_input_from_memory	32	16	50.0%	['fuzz_keyring_kbx', 'fuzz_sigimport', 'fuzz_dump', 'fuzz_verify', 'fuzz_keyimport', 'fuzz_verify_detached', 'fuzz_keyring']
parse_protected_seckey(pgp_key_pkt_t&,sexp::sexp_list_tconst*,charconst*)	145	70	48.27%	['fuzz_keyring_g10']
mem_dest_own_memory(pgp_dest_t*)	32	15	46.87%	['fuzz_keyring_kbx', 'fuzz_keyring_g10']
rnp::DumpContextJson::dump_signature_subpackets(pgp::pkt::Signatureconst&)	34	17	50.0%
rnp::DumpContextJson::dump_signature_pkt(pgp::pkt::Signatureconst&,json_object*)	102	55	53.92%
rnp::DumpContextJson::dump_key(json_object*)	69	32	46.37%
botan_ffi_supports_api	33	10	30.30%	['fuzz_keyring_kbx', 'fuzz_keyring', 'fuzz_keyimport']
Botan_FFI::(anonymousnamespace)::ffi_map_error_type(Botan::ErrorType)	45	9	20.0%
Botan::EMSA::create(std::__1::basic_string_view >)	59	9	15.25%
Botan::EC_Group::EC_group_info(Botan::OIDconst&)	273	102	37.36%
decrypt_secret_key(pgp_key_pkt_t*,charconst*)	71	7	9.859%	['fuzz_keyring_kbx', 'fuzz_keyring', 'fuzz_keyimport']

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file	Reached by	Covered by
	[]	[]
/src/rnp/src/lib/crypto/elgamal.cpp	[]	[]
/src/rnp/src/lib/crypto/ec.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/hash.cpp	['fuzz_keyring_g10']	[]
/usr/local/bin/../include/c++/v1/__iterator/move_iterator.h	[]	[]
/src/rnp/src/lib/crypto/ecdh.h	[]	[]
/src/rnp/src/lib/crypto/rsa.cpp	[]	[]
/src/rnp/src/common/str-utils.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/reducer.h	[]	[]
/src/rnp/src/fuzzing/keyimport.c	['fuzz_keyimport']	['fuzz_keyimport']
/src/rnp/src/librepgp/stream-key.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/rsa.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/cipher_mode.h	[]	[]
/src/rnp/src/lib/crypto/ecdh.cpp	[]	[]
/src/rnp/src/librepgp/stream-armor.cpp	[]	[]
/usr/include/botan-3/botan/pubkey.h	[]	[]
/usr/include/botan-3/botan/bigint.h	[]	[]
/src/rnp/src/libsexpp/src/sexp-depth-manager.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/sm2.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/dsa.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/hash_common.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/system_rng.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/sig_material.hpp	['fuzz_keyring_g10']	[]
/usr/include/botan-3/botan/kdf.h	[]	[]
/usr/include/botan-3/botan/rng.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/key_material.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/exdsa_ecdhkem.cpp	[]	[]
/usr/include/botan-3/botan/symkey.h	[]	[]
/src/rnp/src/lib/crypto/symmetric.cpp	[]	[]
/src/rnp/src/librepgp/stream-sig.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/key.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/libsexpp/src/sexp-object.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/aead.h	[]	[]
/src/rnp/src/lib/crypto/kmac.cpp	[]	[]
/src/rnp/src/lib/utils.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/userid.hpp	[]	[]
/usr/include/botan-3/botan/ec_point.h	[]	[]
/src/rnp/src/lib/../librepgp/stream-sig.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/types.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/kyber.h	[]	[]
/src/rnp/src/librekey/key_store_pgp.cpp	[]	[]
/src/rnp/src/lib/crypto/kyber_ecdh_composite.cpp	[]	[]
/src/rnp/src/common/file-utils.cpp	[]	[]
/src/rnp/src/lib/crypto/backend_version.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/fuzzing/keyring.c	['fuzz_keyring']	['fuzz_keyring']
/src/rnp/src/lib/crypto/dilithium.h	[]	[]
/src/rnp/src/fuzzing/verify_detached.c	['fuzz_verify_detached']	['fuzz_verify_detached']
/src/rnp/src/lib/sig_subpacket.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/fingerprint.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/ecdsa.h	[]	[]
/src/rnp/src/lib/crypto/kyber.cpp	[]	[]
/src/rnp/src/fuzzing/keyring_g10.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/mem.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/include/rekey/rnp_key_store.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/signature.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/common/time-utils.cpp	[]	[]
/src/rnp/src/lib/crypto/dilithium.cpp	[]	[]
/src/rnp/src/libsexpp/src/sexp-simple-string.cpp	[]	[]
/src/rnp/src/lib/enc_material.hpp	[]	[]
/src/rnp/src/lib/crypto/mpi.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/ed25519.h	[]	[]
/usr/include/botan-3/botan/kyber.h	[]	[]
/src/rnp/src/lib/crypto/x25519.cpp	[]	[]
/usr/include/botan-3/botan/mac.h	[]	[]
/src/rnp/src/lib/crypto/dilithium_exdsa_composite.cpp	[]	[]
/src/rnp/src/lib/crypto/mem.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/rng.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/fingerprint.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/kmac.hpp	[]	[]
/src/rnp/src/lib/userid.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/libsexpp/include/sexpp/sexp.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/key_material.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/ed25519.cpp	[]	[]
/src/rnp/src/librekey/rnp_key_store.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/fuzzing/verify.c	['fuzz_verify']	['fuzz_verify']
/src/rnp/src/lib/crypto/dsa_common.cpp	[]	[]
/src/rnp/src/lib/crypto/eddsa.cpp	[]	[]
/src/rnp/src/lib/keygen.hpp	[]	[]
/src/rnp/src/lib/crypto/sha1cd/ubc_check.c	[]	[]
/src/rnp/src/lib/crypto/ecdh_utils.cpp	[]	[]
/usr/include/botan-3/botan/pk_keys.h	[]	[]
/src/rnp/src/fuzzing/keyring_kbx.c	['fuzz_keyring_kbx']	['fuzz_keyring_kbx']
/usr/local/bin/../include/c++/v1/__exception/exception.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/../librepgp/stream-key.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/ecdsa.cpp	[]	[]
/src/rnp/src/libsexpp/src/sexp-input.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/sec_profile.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/pass-provider.cpp	[]	[]
/src/rnp/src/lib/crypto/s2k.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/librekey/key_store_kbx.cpp	[]	[]
/src/rnp/src/lib/../librepgp/stream-common.h	[]	['fuzz_keyring_g10']
/src/rnp/src/libsexpp/src/sexp-char-defs.cpp	[]	[]
/src/rnp/src/lib/key.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/curve_gfp.h	[]	[]
/src/rnp/src/lib/crypto/exdsa_ecdhkem.h	[]	[]
/src/rnp/src/lib/crypto/kyber_ecdh_composite.h	[]	[]
/src/rnp/src/lib/crypto/mpi.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/sphincsplus.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/rawpacket.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/secmem.h	[]	[]
/src/rnp/src/libsexpp/include/sexpp/ext-key-format.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/ec.cpp	[]	[]
/src/rnp/src/librekey/key_store_g10.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/logging.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/sig_material.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/librepgp/stream-common.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/../librepgp/stream-packet.h	[]	[]
/src/rnp/src/lib/utils.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/symmetric_common.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/signature.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/fuzzing/sigimport.c	['fuzz_sigimport']	['fuzz_sigimport']
/src/rnp/src/lib/sec_profile.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/rawpacket.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/dilithium_exdsa_composite.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/kyber_common.cpp	[]	[]
/src/rnp/src/librepgp/stream-packet.h	[]	[]
/src/rnp/src/librekey/kbx_blob.hpp	[]	[]
/src/rnp/src/libsexpp/src/ext-key-format.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/local/bin/../include/c++/v1/string	[]	[]
/src/rnp/src/lib/crypto/sha1cd/sha1.c	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/sig_subpacket.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/fuzzing/dump.c	['fuzz_dump']	['fuzz_dump']
/src/rnp/src/lib/crypto/ec_curves.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/enc_material.cpp	[]	[]
/src/rnp/src/libsexpp/src/sexp-error.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/hash.hpp	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/dsa.cpp	[]	[]
/usr/include/botan-3/botan/dilithium.h	[]	[]
/usr/include/botan-3/botan/sym_algo.h	[]	[]
/src/rnp/src/libsexpp/src/sexp-output.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/buf_comp.h	[]	[]
/src/rnp/src/librepgp/stream-common.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/curve25519.h	[]	[]
/src/rnp/src/lib/crypto/hash_sha1cd.cpp	['fuzz_keyring_g10']	[]
/usr/include/botan-3/botan/ecdh.h	[]	[]
/usr/local/bin/../include/c++/v1/stdexcept	['fuzz_keyring_g10']	[]
/src/rnp/src/librepgp/stream-sig.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/include/botan-3/botan/ecc_key.h	[]	[]
/src/rnp/src/lib/crypto/sm2.h	[]	[]
/src/rnp/src/lib/crypto/hkdf.hpp	[]	[]
/src/rnp/src/lib/crypto/dilithium_common.cpp	[]	[]
/src/rnp/src/lib/keygen.cpp	[]	[]
/src/rnp/src/librepgp/stream-packet.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/sphincsplus.cpp	[]	[]
/src/rnp/src/lib/crypto/cipher.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/usr/local/bin/../include/c++/v1/sstream	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/hkdf.cpp	[]	[]
/src/rnp/src/libsexpp/include/sexpp/sexp-error.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/librekey/g23_sexp.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/librepgp/stream-key.h	[]	[]
/src/rnp/src/lib/crypto/elgamal.h	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/key-provider.h	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/key-provider.cpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/lib/crypto/cipher_botan.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/hkdf_botan.cpp	[]	[]
/src/rnp/src/lib/crypto/kmac_botan.cpp	[]	[]
/src/rnp/src/lib/crypto/signatures.cpp	['fuzz_keyring_g10']	[]
/src/rnp/src/lib/crypto/botan_utils.hpp	['fuzz_keyring_g10']	['fuzz_keyring_g10']
/src/rnp/src/librepgp/stream-armor.h	[]	[]
/src/rnp/src/lib/pass-provider.h	[]	[]

Directories in report

Directory
/src/rnp/src/libsexpp/src/
/usr/local/bin/../include/c++/v1/__iterator/
/src/rnp/src/fuzzing/
/src/rnp/src/librepgp/
/src/rnp/src/lib/
/src/rnp/src/librekey/
/src/rnp/src/lib/crypto/
/usr/include/botan-3/botan/
/src/rnp/src/lib/crypto/sha1cd/
/src/rnp/include/rekey/
/usr/local/bin/../include/c++/v1/__exception/
/src/rnp/src/lib/../librepgp/
/usr/local/bin/../include/c++/v1/
/src/rnp/src/common/
/src/rnp/src/libsexpp/include/sexpp/