-
Notifications
You must be signed in to change notification settings - Fork 39
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
Ported Veracruz to Linux #116
Ported Veracruz to Linux #116
Conversation
7ecab21
to
3663685
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
6c12266
to
f63e358
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
e4cbb43
to
00cdf86
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
00cdf86
to
e9bb223
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
e9bb223
to
f5f78df
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
f5f78df
to
0547d71
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
0547d71
to
533584b
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
a784876
to
46e16fc
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
791bf99
to
81d3626
Compare
c86ab91
to
7fc258b
Compare
7fc258b
to
92438c9
Compare
e4036b1
to
902bc28
Compare
3cda5f7
to
2c7621a
Compare
ce5d08d
to
b5e71e6
Compare
…testation - Linux Root Enclave implemented for co-ordinating spawning of application enclaves. Note most attestation-related material is actually handled by the Linux Root Enclave, rather than the application (runtime) enclave, as attestation for Linux is "fake"/insecure, and the Root enclave seems a more convenient place to put it. - Proxy attestation is using Derek's new CA-based attestation system. - New build targets of note: linux linux-veracruz-server-test linux-veracruz-client-test linux-veracruz-test linux-cli. - Added Linux buildspec to the CI configuration. - Minor rearrangement of material in veracruz-utils to accommodate Linux-related material. Note that Derek's recent changes, removing the Nitro root enclaves, has led to some duplication being reintroduced into veracruz-utils (owing to slight differences between the messages being sent to various enclaves in Linux/Nitro. When the Linux root enclave is removed (TODO) these duplications will be eliminated, streamlining this material. - Slight change in the naming of features in e.g. proxy-attestation-server to mark the fact that the TrustZone backend is now not the only backend using PSA attestation (even if it is "fake").
d0e0cbe
to
72a4fb0
Compare
+1+1 = +1 reached, merging. |
Note most attestation-related material is actually handled by the Linux Root Enclave, rather
than the application (runtime) enclave, as attestation for Linux is "fake"/insecure, and
the Root enclave seems a more convenient place to put it.
linux-veracruz-test linux-cli.
material. Note that Derek's recent changes, removing the Nitro root enclaves, has led
to some duplication being reintroduced into veracruz-utils (owing to slight differences
between the messages being sent to various enclaves in Linux/Nitro. When the Linux root
enclave is removed (TODO) these duplications will be eliminated, streamlining this material.
fact that the TrustZone backend is now not the only backend using PSA attestation (even
if it is "fake").