High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers

61 / 1112

Cyclomatic complexity statically reachable by fuzzers

198 / 3558

Runtime code coverage of functions

263 / 1112

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_sign_verify_with_valid_key

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	139	53.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	119	46.1%
All colors	258	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
29	88	model_signing.hashing.Config.hash	call site: 00088	model_signing.hashing.Config._build_sharded_file_hasher_factory._factory
21	236	model_signing.verifying.Config.verify	call site: 00236	model_signing.verifying.Config._get_manifest_diff
16	133	model_signing._signing.sign_sigstore_pb.pae	call site: 00133	model_signing._signing.sign_pkcs11.CertSigner._get_verification_material
9	168	model_signing._signing.sign_ec_key.Signer.sign	call site: 00168	model_signing._signing.sign_certificate.Signer._get_verification_material
9	219	model_signing.verifying.Config._guess_hashing_config	call site: 00219	model_signing.hashing.Config.use_shard_serialization
8	46	model_signing.hashing.Config.hash	call site: 00046	model_signing.hashing.Config._build_sharded_file_hasher_factory._factory
8	151	model_signing.signing.Config.sign	call site: 00151	model_signing._signing.sign_sigstore.Signer._get_identity_token
7	33	...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput	call site: 00033	model_signing.signing.Config.use_sigstore_signer
5	187	...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput	call site: 00187	model_signing._signing.sign_sigstore.Signature.read
4	82	model_signing._serialization.file.Serializer.serialize	call site: 00082	.list
4	162	model_signing._signing.sign_ec_key.Signer.sign	call site: 00162	model_signing._signing.sign_sigstore_pb.pae
4	203	model_signing.manifest.SerializationType.from_args	call site: 00203	bytes.fromhex

Runtime coverage analysis

Covered functions

368

Functions that are reachable but not covered

99

Reachable functions

151

Percentage of reachable functions covered

34.44%

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
/	1
...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key	15
model_signing.signing	12
model_signing.hashing	21
model_signing._serialization.file	22
model_signing._hashing.memory	2
model_signing.manifest	3
model_signing._signing.sign_ec_key	12
model_signing._signing.sign_sigstore	16
model_signing._serialization.file_shard	27
model_signing._hashing.io	2
model_signing._serialization.serialization	5
model_signing._signing.signing	18
model_signing._signing.sign_pkcs11	18
model_signing._signing.sign_sigstore_pb	1
cryptography.hazmat.primitives.asymmetric.ec	1
model_signing._signing.sign_certificate	6
model_signing.verifying	18

Fuzzer: fuzz_sign_with_invalid_key

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	104	56.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	80	43.4%
All colors	184	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
29	91	model_signing.hashing.Config.hash	call site: 00091	model_signing.hashing.Config._build_sharded_file_hasher_factory._factory
19	161	model_signing.signing.Config.sign	call site: 00161	model_signing._signing.sign_pkcs11.CertSigner._get_verification_material
9	141	model_signing._signing.sign_ec_key.Signer.sign	call site: 00141	model_signing._signing.sign_certificate.Signer._get_verification_material
8	35	model_signing._signing.sign_ec_key.Signer.__init__	call site: 00035	model_signing.signing.Config.sign
8	49	model_signing.hashing.Config.hash	call site: 00049	model_signing.hashing.Config._build_sharded_file_hasher_factory._factory
8	151	model_signing.signing.Config.sign	call site: 00151	model_signing._signing.sign_sigstore.Signer._get_identity_token
4	85	model_signing._serialization.file.Serializer.serialize	call site: 00085	.list
3	7	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00007	.open
3	136	model_signing._signing.sign_sigstore_pb.pae	call site: 00136	cryptography.hazmat.primitives.asymmetric.ec.ECDSA.__init__
2	1	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00001	fdp.ConsumeIntInRange
2	4	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00004	tempfile.TemporaryDirectory
2	13	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00013	model_signing.signing.Config.__init__

Runtime coverage analysis

Covered functions

367

Functions that are reachable but not covered

79

Reachable functions

119

Percentage of reachable functions covered

33.61%

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
/	1
...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key	11
model_signing.signing	12
model_signing.hashing	17
model_signing._serialization.file	22
model_signing._hashing.memory	2
model_signing.manifest	2
model_signing._signing.sign_ec_key	11
model_signing._signing.sign_sigstore	12
model_signing._serialization.file_shard	27
model_signing._hashing.io	2
model_signing._serialization.serialization	5
model_signing._signing.signing	7
model_signing._signing.sign_sigstore_pb	2
cryptography.hazmat.primitives.asymmetric.ec	1
model_signing._signing.sign_certificate	6
model_signing._signing.sign_pkcs11	18

Fuzzer: fuzz_sign_with_valid_key_verify_with_invalid_key

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	159	58.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	111	41.1%
All colors	270	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
29	87	model_signing.hashing.Config.hash	call site: 00087	model_signing.hashing.Config._build_sharded_file_hasher_factory._factory
21	132	model_signing._signing.sign_sigstore_pb.pae	call site: 00132	model_signing._signing.sign_pkcs11.CertSigner._get_verification_material
21	248	model_signing.verifying.Config.verify	call site: 00248	model_signing.verifying.Config._get_manifest_diff
10	0	EP	call site: 00000	atheris.FuzzedDataProvider
9	176	model_signing._signing.sign_ec_key.Signer._get_verification_material	call site: 00176	model_signing._signing.sign_certificate.Signer._get_verification_material
9	231	model_signing.verifying.Config._guess_hashing_config	call site: 00231	model_signing.hashing.Config.use_shard_serialization
8	49	model_signing.hashing.Config.hash	call site: 00049	model_signing.hashing.Config._build_sharded_file_hasher_factory._factory
8	154	model_signing.signing.Config.sign	call site: 00154	model_signing._signing.sign_sigstore.Signer._get_identity_token
7	32	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00032	model_signing.signing.Config.use_sigstore_signer
5	200	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00200	model_signing._signing.sign_sigstore.Signature.read
4	81	model_signing._serialization.file.Serializer.serialize	call site: 00081	.list
4	165	model_signing._signing.sign_ec_key.Signer.sign	call site: 00165	model_signing._signing.sign_sigstore_pb.pae

Runtime coverage analysis

Covered functions

368

Functions that are reachable but not covered

100

Reachable functions

154

Percentage of reachable functions covered

35.06%

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
/	1
...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key	13
model_signing.signing	12
model_signing.hashing	21
model_signing._serialization.file	22
model_signing._hashing.memory	2
model_signing.manifest	3
model_signing._signing.sign_ec_key	17
model_signing._signing.sign_sigstore	17
model_signing._serialization.file_shard	27
model_signing._hashing.io	2
model_signing._serialization.serialization	5
model_signing._signing.signing	17
model_signing._signing.sign_pkcs11	22
model_signing._signing.sign_sigstore_pb	1
cryptography.hazmat.primitives.asymmetric.ec	1
model_signing._signing.sign_certificate	6
model_signing.verifying	18

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
cryptography.hazmat.primitives.serialization.ssh.SSHCertificateBuilder.sign	cryptography.hazmat.primitives.serialization.ssh	2	['N/A', 'N/A']	5	0	37	11	7	53	0	177	165
model_signing._signing.pkcs11uri.Pkcs11URI.login	model_signing._signing.pkcs11uri	1	['N/A']	3	0	2	4	5	31	3	108	96
cryptography.hazmat.primitives.serialization.ssh.load_ssh_private_key	cryptography.hazmat.primitives.serialization.ssh	4	['N/A', 'N/A', 'N/A', 'N/A']	3	0	12	15	9	35	0	116	82
cryptography.x509.name._RFC4514NameParser._parse_na	cryptography.x509.name	1	['N/A']	4	0	1	2	4	18	3	62	53
cryptography.fernet.Fernet._decrypt_data	cryptography.fernet	4	['N/A', 'N/A', 'N/A', 'N/A']	4	0	1	3	4	25	2	81	50
model_signing._signing.pkcs11uri.Pkcs11URI.parse	model_signing._signing.pkcs11uri	2	['N/A', 'N/A']	2	0	5	5	5	17	3	59	43
model_signing._signing.sign_certificate.Verifier._verify_certificates	model_signing._signing.sign_certificate	3	['N/A', 'N/A', 'N/A']	2	0	5	4	5	10	2	35	35

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

Functions statically reachable by fuzzers

127 / 1112

Cyclomatic complexity statically reachable by fuzzers

443 / 3558

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/model-transparency/tests/fuzzing/fuzz_sign_verify_with_valid_key.py

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=['model_signing.hashing.Config.hash', 'model_signing.verifying.Config.verify', 'model_signing._signing.sign_sigstore_pb.pae', 'model_signing._signing.sign_ec_key.Signer.sign', 'model_signing.verifying.Config._guess_hashing_config', 'model_signing.signing.Config.sign', '...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput', 'model_signing._serialization.file.Serializer.serialize']

/src/model-transparency/tests/fuzzing/fuzz_sign_with_invalid_key.py

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=['model_signing.hashing.Config.hash', 'model_signing.signing.Config.sign', 'model_signing._signing.sign_ec_key.Signer.sign', 'model_signing._signing.sign_ec_key.Signer.__init__', 'model_signing._serialization.file.Serializer.serialize', '...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput', 'model_signing._signing.sign_sigstore_pb.pae']

/src/model-transparency/tests/fuzzing/fuzz_sign_with_valid_key_verify_with_invalid_key.py

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=['model_signing.hashing.Config.hash', 'model_signing._signing.sign_sigstore_pb.pae', 'model_signing.verifying.Config.verify', 'model_signing._signing.sign_ec_key.Signer._get_verification_material', 'model_signing.verifying.Config._guess_hashing_config', 'model_signing.signing.Config.sign', '...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput']

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
os.path.isdir	290	131	45.17%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
cryptography.hazmat.primitives.serialization.ssh.load_ssh_private_key	68	0	0.0%	[]
cryptography.hazmat.primitives.serialization.ssh._serialize_ssh_private_key	52	5	9.615%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
cryptography.hazmat.primitives.serialization.ssh._load_ssh_public_identity	56	0	0.0%	[]
cryptography.hazmat.primitives.serialization.ssh.SSHCertificateBuilder.sign	85	0	0.0%	[]
re.match	2168	465	21.44%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
val.to_bytes	91	38	41.75%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
point.tobytes	95	43	45.26%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
typing_extensions.override	1709	555	32.47%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
resources.append	1640	2	0.121%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
statement.Statement	31	13	41.93%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
asn1crypto.keys.PublicKeyInfo.dump	350	177	50.57%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
google.protobuf.json_format.MessageToJson	492	133	27.03%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
hash.finalize	73	27	36.98%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
i.isdigit	141	16	11.34%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
OpenSSL.crypto.X509StoreContext	880	207	23.52%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
signer.sign_dsse	84	30	35.71%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
p.is_absolute	46	21	45.65%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']
r.pop	109	13	11.92%	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key']

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
	[]	[]
cryptography.hazmat.primitives.cmac	[]	[]
model_signing._signing.sign_pkcs11	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
PyKCS11	[]	[]
random	[]	[]
cryptography.hazmat.bindings._rust	[]	[]
...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key	['fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key	['fuzz_sign_with_invalid_key']	[]
cryptography.hazmat.primitives.kdf.hkdf	[]	[]
cryptography.hazmat.decrepit.ciphers.algorithms	[]	[]
json	[]	[]
model_signing._signing.sign_sigstore_pb	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives.padding	[]	[]
cryptography.hazmat.primitives.asymmetric.ed25519	[]	[]
cryptography.hazmat.primitives.twofactor	[]	[]
cryptography.hazmat.backends.openssl.backend	[]	[]
cryptography.hazmat.primitives.kdf.argon2	[]	[]
shutil	[]	[]
cryptography.x509.ocsp	[]	[]
cryptography.hazmat.primitives.serialization	[]	[]
hashlib	[]	[]
cryptography.hazmat.primitives.serialization.ssh	[]	[]
model_signing.hashing	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives.kdf.x963kdf	[]	[]
model_signing.manifest	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
hmac	[]	[]
cryptography.hazmat.primitives.kdf	[]	[]
sigstore	[]	[]
threading	[]	[]
stat	[]	[]
cryptography.fernet	[]	[]
model_signing	[]	[]
asn1crypto	[]	[]
cryptography.hazmat.primitives.kdf.concatkdf	[]	[]
model_signing._hashing.memory	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography	[]	[]
model_signing._cli	[]	[]
sigstore_protobuf_specs	[]	[]
itertools	[]	[]
model_signing.__main__	[]	[]
cryptography.hazmat.primitives.asymmetric.ec	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
model_signing._serialization.file_shard	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
atexit	[]	[]
cryptography.hazmat.primitives._cipheralgorithm	[]	[]
model_signing.verifying	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
re	[]	[]
model_signing._signing.sign_sigstore	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives.twofactor.hotp	[]	[]
cryptography.hazmat.primitives.asymmetric.dh	[]	[]
cryptography.hazmat.primitives.asymmetric.dsa	[]	[]
cryptography.x509.oid	[]	[]
cryptography.hazmat	[]	[]
model_signing._hashing.io	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.exceptions	[]	[]
cryptography.x509.name	[]	[]
cryptography.hazmat.primitives.hmac	[]	[]
cryptography.x509	[]	[]
cryptography.hazmat._oid	[]	[]
cryptography.hazmat.primitives.twofactor.totp	[]	[]
cryptography.x509.verification	[]	[]
logging	[]	[]
cryptography.hazmat.primitives.asymmetric.types	[]	[]
cryptography.hazmat.primitives.asymmetric.utils	[]	[]
urllib	[]	[]
	[]	[]
opentelemetry	[]	[]
cryptography.hazmat.primitives.ciphers.modes	[]	[]
io	[]	[]
model_signing._hashing	[]	[]
cryptography.x509.extensions	[]	[]
model_signing._signing	[]	[]
OpenSSL	[]	[]
cryptography.hazmat.primitives.asymmetric.padding	[]	[]
email	[]	[]
cryptography.hazmat.primitives	[]	[]
cryptography.hazmat.primitives.serialization.pkcs12	[]	[]
cryptography.hazmat.bindings.openssl.binding	[]	[]
...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key	['fuzz_sign_verify_with_valid_key']	[]
cryptography.hazmat.primitives.asymmetric.rsa	[]	[]
tempfile	[]	[]
cryptography.hazmat.primitives.ciphers.algorithms	[]	[]
base64	[]	[]
cryptography.hazmat.decrepit	[]	[]
model_signing._signing.sign_ec_key	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
glob	[]	[]
math	[]	[]
cryptography.hazmat.primitives.constant_time	[]	[]
cryptography.hazmat.bindings.openssl._conditional	[]	[]
cryptography.hazmat.backends	[]	[]
warnings	[]	[]
google	[]	[]
cryptography.hazmat.bindings	[]	[]
cryptography.hazmat.primitives.kdf.kbkdf	[]	[]
cryptography.hazmat.primitives.ciphers.aead	[]	[]
cryptography.hazmat.backends.openssl	[]	[]
cryptography.x509.base	[]	[]
cryptography.hazmat.primitives.poly1305	[]	[]
cryptography.hazmat.primitives.keywrap	[]	[]
cryptography.hazmat.primitives.asymmetric.x25519	[]	[]
pathlib	[]	[]
binascii	[]	[]
types	[]	[]
certifi	[]	[]
model_signing.signing	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.bindings.openssl	[]	[]
model_signing._hashing.hashing	[]	[]
sys	[]	[]
cryptography.x509.general_name	[]	[]
datetime	[]	[]
cryptography.hazmat.primitives.asymmetric.ed448	[]	[]
cryptography.x509.certificate_transparency	[]	[]
click	[]	[]
model_signing._signing.pkcs11uri	[]	[]
model_signing._signing.sign_certificate	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
time	[]	[]
cryptography.hazmat.primitives.serialization.base	[]	[]
cryptography.hazmat.primitives._asymmetric	[]	[]
cryptography.hazmat.primitives.asymmetric	[]	[]
model_signing._serialization	[]	[]
typing	[]	[]
model_signing._signing.signing	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
atheris	[]	[]
cryptography.hazmat.primitives.ciphers.base	[]	[]
cryptography.hazmat.primitives.serialization.pkcs7	[]	[]
model_signing._serialization.file	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives.kdf.scrypt	[]	[]
cryptography.hazmat.primitives._serialization	[]	[]
cryptography.hazmat.decrepit.ciphers	[]	[]
cryptography.hazmat.primitives.kdf.pbkdf2	[]	[]
bcrypt	[]	[]
os	[]	[]
cryptography.__about__	[]	[]
cryptography.hazmat.primitives.hashes	[]	[]
model_signing._serialization.serialization	['fuzz_sign_verify_with_valid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives.asymmetric.x448	[]	[]
cryptography.hazmat.primitives.ciphers	[]	[]
cryptography.utils	[]	[]

Directories in report

Directory