Skip to content

Fuzzing test cases for PKCS#8 v2 support#763

Merged
skmcgrail merged 1 commit intoaws:pkcs8v2from
skmcgrail:pkcs8v2_fuzz
Jan 23, 2023
Merged

Fuzzing test cases for PKCS#8 v2 support#763
skmcgrail merged 1 commit intoaws:pkcs8v2from
skmcgrail:pkcs8v2_fuzz

Conversation

@skmcgrail
Copy link
Copy Markdown
Member

Description of changes:

Adds fuzzing coverage for the PKCS#8 v2 support. The inputs were seeded from the associated EVP_KEY tests cases added in the prior PKCS#8 pull request. I have broken up the fuzzing between pkcs8 and pkcs8_v2 to ensure the fuzzer can reach EVP_marshal_private_key_v2 rather then it potentially being unreachable if it was in a combined function testing both EVP_marshal_private_key and EVP_marshal_private_key_v2.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and
the ISC license.

@@ -21,6 +21,7 @@ fuzzer(privkey)
fuzzer(cert)
fuzzer(spki)
fuzzer(pkcs8)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if we should rename this to pkcs8_v1, but the current version does correspond with EVP_marshal_private_key/EVP_marshal_private_key_v2

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to bias towards leaving it the same for now to stay consistent with BoringSSL upstream. Can revisit later if needed.

@skmcgrail skmcgrail merged commit 49d1213 into aws:pkcs8v2 Jan 23, 2023
@skmcgrail skmcgrail deleted the pkcs8v2_fuzz branch January 23, 2023 17:29
R3hankhan123 pushed a commit to R3hankhan123/aws-lc that referenced this pull request Aug 29, 2025
* Fix MacOS w/ CMake 4.0 build

* Cleanup CI environment variable usage

* MacOS - test w/ latest CMake

* Refactor environment variable handling

* Use release builds for cross. Per Wine/x86_64-pc-windows-gnu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants