Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Import of AWS-LC Cryptofuzz CI #342

Merged
merged 1 commit into from
Nov 10, 2023
Merged

Conversation

geedo0
Copy link
Contributor

@geedo0 geedo0 commented Oct 27, 2023

Issue #, if available:
CryptoAlg-2133

Description of changes:
This imports a pristine copy of the AWS-LC Cryptofuzz CI infrastructure so that
it'll be a lot easier to review the changes made to support ACCP.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

tests/ci/cdk/cdk/accp_github_fuzz_ci_stack.py Show resolved Hide resolved
# codebuild_$identifier.
# https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codebuild-project-projectfilesystemlocation.html
#
# TODO: add this to the CDK project above when it supports EfsFileSystemLocation
Copy link
Contributor

Choose a reason for hiding this comment

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

note for later PR: does CDK support this now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will look into it.

fi
}

function build_and_test_ssl_runner_valgrind {
Copy link
Contributor

Choose a reason for hiding this comment

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

note for later PR: a lot of the stuff in this file seems AWS-LC-specific. we should prune out what we can.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yup, you'll see that in the next PR.

@@ -0,0 +1,19 @@
# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
Copy link
Contributor

Choose a reason for hiding this comment

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

what's this dockerfile used for?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As a layer that has clang installed/configured for the cryptofuzz container. In LC, they use it for other stuff but if we are inclined we can flatten the hierarchy a bit to avoid this. Layering is best practice within the Docker ecosystem though.

Copy link
Contributor

@WillChilds-Klein WillChilds-Klein Nov 9, 2023

Choose a reason for hiding this comment

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

no objections to layering, but it looks like tests/ci/docker_images/linux-x86/amazonlinux-2_clang-11x_cryptofuzz/Dockerfile doesn't depend on this or images produced by it, instead referencing amazonlinux-2023:clang-15x

(no need to address until next PR in the series)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This PR is direct copy of the source material (with some file renaming to make things diff better). The next PR updates the references.

# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
# SPDX-License-Identifier: Apache-2.0 OR ISC

FROM amazonlinux-2023:clang-15x
Copy link
Contributor

Choose a reason for hiding this comment

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

the file is amazonlinux-2_clang-11x_cryptofuzz but we're basing this on amazonlinux-2023:clang-15x. is the file misnamed?

(no need to address until next PR in the series)

This directly imports the related CI source for Cryptofuzz from AWS-LC so that the ACCP specific changes show up better in PR and the source history.
@geedo0 geedo0 merged commit 430b607 into corretto:main Nov 10, 2023
8 checks passed
@geedo0 geedo0 deleted the import branch November 10, 2023 16:00
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