-
Notifications
You must be signed in to change notification settings - Fork 60
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
doc: provide a guide for how to install CC with IBM Secure Execution #329
doc: provide a guide for how to install CC with IBM Secure Execution #329
Conversation
0322888
to
9823238
Compare
For reviewers, you can find the referred documentation in the section |
7c51ca1
to
b25f530
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me. Thanks!
e8ca599
to
17e3431
Compare
Hi @BbolroC ! I don't have a SystemZ to test the guide so I only reviewed the text. I've got two suggestions to you:
The binary is found in |
@BbolroC overall lgtm but I just found some misspelling in |
Thanks @GabyCT for the feedback. Actually, |
Thanks @wainersm for the feedback. I will reflect it asap. 😉 |
Due to the limitation that a public key used to encrypt a secure image is associated with a machine specific private key, a user cannot install and run a confidential container with IBM Secure Execution from release. This is to provide a guide for how to achieve the goals above with a custom build. Signed-off-by: Hyounggyu Choi <[email protected]>
17e3431
to
67f1427
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot Choi!
/LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @BbolroC !
Due to the limitation that a public key used to encrypt a secure image is associated with a machine specific private key, a user cannot install and run a confidential container with IBM Secure Execution from release.
This is to provide a guide for how to achieve the goals above with a custom build.
Signed-off-by: Hyounggyu Choi [email protected]