High level conclusions

Fuzzer fuzz_sign_with_invalid_key is blocked:

The runtime code coverage of fuzz_sign_with_invalid_key covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

16 / 1114

Cyclomatic complexity statically reachable by fuzzers

55 / 3564

Runtime code coverage of functions

264 / 1114

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_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	49	61.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	31	38.7%
All colors	80	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
21	58	model_signing.manifest.Manifest.resource_descriptors	call site: 00058	model_signing.verifying.Config._get_manifest_diff
10	0	EP	call site: 00000	atheris.FuzzedDataProvider
5	22	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00022	model_signing._signing.sign_sigstore.Signature.read
4	38	model_signing.manifest.SerializationType.from_args	call site: 00038	bytes.fromhex
3	53	model_signing.verifying.Config.verify	call site: 00053	model_signing.manifest.Manifest.resource_descriptors
2	35	model_signing._signing.signing.Verifier.verify	call site: 00035	model_signing._signing.signing.dsse_payload_to_manifest_compat
1	12	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00012	os.path.join
1	14	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00014	f.write
1	19	model_signing.verifying.Config.use_elliptic_key_verifier	call site: 00019	public_key_path.read_bytes
1	32	model_signing._signing.signing.Verifier.verify	call site: 00032	typing.cast

Runtime coverage analysis

Covered functions

368

Functions that are reachable but not covered

33

Reachable functions

50

Percentage of reachable functions covered

34.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
/	1
...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key	12
model_signing.verifying	14
model_signing._signing.sign_ec_key	2
model_signing._signing.sign_sigstore	4
model_signing._signing.signing	14
model_signing.manifest	3
model_signing._hashing.memory	1

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	37	48.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	51.9%
All colors	77	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
21	55	model_signing.manifest.Manifest.resource_descriptors	call site: 00055	model_signing.verifying.Config._get_manifest_diff
5	20	...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput	call site: 00020	model_signing._signing.sign_sigstore.Signature.read
4	35	model_signing.manifest.SerializationType.from_args	call site: 00035	bytes.fromhex
3	50	model_signing.verifying.Config.verify	call site: 00050	model_signing.manifest.Manifest.resource_descriptors
2	32	model_signing._signing.signing.Verifier.verify	call site: 00032	model_signing._signing.signing.dsse_payload_to_manifest_compat
1	17	model_signing.verifying.Config.use_elliptic_key_verifier	call site: 00017	public_key_path.read_bytes
1	29	model_signing._signing.signing.Verifier.verify	call site: 00029	typing.cast

Runtime coverage analysis

Covered functions

368

Functions that are reachable but not covered

32

Reachable functions

50

Percentage of reachable functions covered

36.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
/	1
...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key	14
model_signing.verifying	14
model_signing._signing.sign_ec_key	2
model_signing._signing.sign_sigstore	4
model_signing._signing.signing	13
model_signing.manifest	3
model_signing._hashing.memory	1

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	9	52.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	47.0%
All colors	17	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
3	7	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00007	.open
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
1	13	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00013	os.path.join
1	15	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00015	signer.sign

Runtime coverage analysis

Covered functions

367

Functions that are reachable but not covered

11

Reachable functions

11

Percentage of reachable functions covered

0.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
/	1
...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key	10

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']	6	0	37	11	7	52	0	174	165
model_signing._serialization.file_shard.Serializer.serialize	model_signing._serialization.file_shard	4	['N/A', 'N/A', 'N/A', 'N/A']	4	0	5	5	5	40	2	128	110
model_signing._signing.pkcs11uri.Pkcs11URI.login	model_signing._signing.pkcs11uri	1	['N/A']	4	0	2	4	5	31	2	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']	4	0	12	15	9	35	0	116	82
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']	3	0	5	5	5	17	2	59	43
cryptography.x509.name._RFC4514NameParser._parse_na	cryptography.x509.name	1	['N/A']	4	0	1	2	4	13	3	43	37
model_signing._signing.sign_certificate.Verifier._verify_certificates	model_signing._signing.sign_certificate	3	['N/A', 'N/A', 'N/A']	3	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

91 / 1114

Cyclomatic complexity statically reachable by fuzzers

327 / 3564

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_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.manifest.Manifest.resource_descriptors', '...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput', 'model_signing.manifest.SerializationType.from_args', 'model_signing.verifying.Config.verify', 'model_signing._signing.signing.Verifier.verify', 'model_signing.verifying.Config.use_elliptic_key_verifier']

/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.manifest.Manifest.resource_descriptors', '...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput', 'model_signing.manifest.SerializationType.from_args', 'model_signing.verifying.Config.verify', 'model_signing._signing.signing.Verifier.verify', 'model_signing.verifying.Config.use_elliptic_key_verifier']

/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-transparency.tests.fuzzing.fuzz_sign_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_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
signer.sign_dsse	84	30	35.71%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_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_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_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_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
val.to_bytes	91	38	41.75%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
point.tobytes	95	43	45.26%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
typing_extensions.override	1709	555	32.47%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
OpenSSL.crypto.X509StoreContext	880	207	23.52%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
resources.append	1640	2	0.121%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
statement.Statement	31	13	41.93%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
google.protobuf.json_format.MessageToJson	492	133	27.03%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
asn1crypto.keys.PublicKeyInfo.dump	350	177	50.57%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
hash.finalize	73	27	36.98%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
i.isdigit	141	16	11.34%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
p.is_absolute	46	21	45.65%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key']
r.pop	109	13	11.92%	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_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.exceptions	[]	[]
cryptography.hazmat._oid	[]	[]
cryptography.hazmat.primitives.serialization.pkcs12	[]	[]
cryptography	[]	[]
itertools	[]	[]
cryptography.x509.general_name	[]	[]
asn1crypto	[]	[]
cryptography.hazmat.primitives.asymmetric.x25519	[]	[]
cryptography.__about__	[]	[]
model_signing._hashing.io	[]	[]
atexit	[]	[]
model_signing._serialization.serialization	[]	[]
sigstore_protobuf_specs	[]	[]
...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key	['fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives.twofactor.hotp	[]	[]
cryptography.hazmat.decrepit.ciphers	[]	[]
glob	[]	[]
cryptography.hazmat.decrepit.ciphers.algorithms	[]	[]
model_signing._signing.sign_pkcs11	[]	[]
model_signing.verifying	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_verify_with_valid_key']	[]
hashlib	[]	[]
cryptography.x509	[]	[]
sys	[]	[]
cryptography.hazmat.primitives.ciphers.modes	[]	[]
cryptography.x509.certificate_transparency	[]	[]
cryptography.hazmat.backends.openssl.backend	[]	[]
base64	[]	[]
cryptography.hazmat.primitives.kdf.scrypt	[]	[]
warnings	[]	[]
urllib	[]	[]
model_signing._serialization	[]	[]
threading	[]	[]
cryptography.x509.base	[]	[]
cryptography.hazmat.primitives.twofactor.totp	[]	[]
cryptography.hazmat	[]	[]
re	[]	[]
typing	[]	[]
cryptography.hazmat.primitives.serialization.pkcs7	[]	[]
cryptography.hazmat.primitives.ciphers.algorithms	[]	[]
model_signing	[]	[]
cryptography.hazmat.primitives.ciphers.base	[]	[]
model_signing._serialization.file_shard	[]	[]
datetime	[]	[]
certifi	[]	[]
cryptography.hazmat.primitives.asymmetric.utils	[]	[]
tempfile	[]	[]
cryptography.x509.ocsp	[]	[]
cryptography.hazmat.backends	[]	[]
cryptography.hazmat.backends.openssl	[]	[]
cryptography.hazmat.primitives.asymmetric.x448	[]	[]
sigstore	[]	[]
model_signing.hashing	[]	[]
cryptography.hazmat.primitives.asymmetric	[]	[]
cryptography.hazmat.primitives.asymmetric.types	[]	[]
cryptography.x509.verification	[]	[]
model_signing._signing.pkcs11uri	[]	[]
opentelemetry	[]	[]
PyKCS11	[]	[]
model_signing._hashing.hashing	[]	[]
model_signing._signing.signing	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_verify_with_valid_key']	[]
cryptography.hazmat.primitives.hashes	[]	[]
model_signing._signing.sign_certificate	[]	[]
cryptography.hazmat.primitives._asymmetric	[]	[]
cryptography.hazmat.primitives.serialization.base	[]	[]
cryptography.hazmat.bindings.openssl.binding	[]	[]
logging	[]	[]
cryptography.x509.extensions	[]	[]
cryptography.utils	[]	[]
cryptography.hazmat.primitives.constant_time	[]	[]
cryptography.hazmat.primitives.twofactor	[]	[]
cryptography.hazmat.primitives.ciphers.aead	[]	[]
model_signing._signing	[]	[]
cryptography.hazmat.primitives.serialization.ssh	[]	[]
cryptography.hazmat.primitives._serialization	[]	[]
cryptography.hazmat.decrepit	[]	[]
atheris	[]	[]
	[]	[]
cryptography.hazmat.primitives.kdf.argon2	[]	[]
model_signing.__main__	[]	[]
cryptography.hazmat.bindings	[]	[]
cryptography.hazmat.primitives.poly1305	[]	[]
...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key	['fuzz_sign_verify_with_valid_key']	[]
shutil	[]	[]
cryptography.hazmat.primitives._cipheralgorithm	[]	[]
click	[]	[]
email	[]	[]
model_signing._hashing.memory	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_verify_with_valid_key']	[]
model_signing._serialization.file	[]	[]
json	[]	[]
cryptography.hazmat.primitives.keywrap	[]	[]
cryptography.hazmat.primitives.kdf	[]	[]
model_signing._hashing	[]	[]
cryptography.x509.oid	[]	[]
cryptography.hazmat.primitives.asymmetric.ed25519	[]	[]
cryptography.hazmat.primitives.asymmetric.ed448	[]	[]
model_signing._signing.sign_sigstore_pb	[]	[]
OpenSSL	[]	[]
cryptography.hazmat.primitives.hmac	[]	[]
cryptography.hazmat.primitives.kdf.kbkdf	[]	[]
types	[]	[]
model_signing._cli	[]	[]
cryptography.hazmat.primitives.asymmetric.rsa	[]	[]
cryptography.hazmat.primitives.asymmetric.ec	[]	[]
model_signing.signing	[]	[]
math	[]	[]
cryptography.hazmat.bindings._rust	[]	[]
io	[]	[]
cryptography.hazmat.primitives.asymmetric.padding	[]	[]
cryptography.hazmat.primitives.cmac	[]	[]
cryptography.fernet	[]	[]
model_signing._signing.sign_sigstore	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_verify_with_valid_key']	[]
cryptography.hazmat.primitives.asymmetric.dsa	[]	[]
pathlib	[]	[]
cryptography.hazmat.primitives.serialization	[]	[]
model_signing._signing.sign_ec_key	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_verify_with_valid_key']	[]
bcrypt	[]	[]
cryptography.hazmat.primitives.kdf.pbkdf2	[]	[]
os	[]	[]
cryptography.hazmat.primitives.kdf.x963kdf	[]	[]
cryptography.hazmat.primitives.kdf.hkdf	[]	[]
binascii	[]	[]
random	[]	[]
cryptography.hazmat.primitives	[]	[]
time	[]	[]
stat	[]	[]
cryptography.hazmat.primitives.kdf.concatkdf	[]	[]
google	[]	[]
cryptography.x509.name	[]	[]
cryptography.hazmat.bindings.openssl	[]	[]
model_signing.manifest	['fuzz_sign_with_valid_key_verify_with_invalid_key', 'fuzz_sign_verify_with_valid_key']	[]
...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key	['fuzz_sign_with_invalid_key']	[]
cryptography.hazmat.primitives.padding	[]	[]
cryptography.hazmat.bindings.openssl._conditional	[]	[]
hmac	[]	[]
cryptography.hazmat.primitives.asymmetric.dh	[]	[]
cryptography.hazmat.primitives.ciphers	[]	[]

Directories in report

Directory