github/confidential-containers
1
0
Fork 0
mirror of https://github.com/confidential-containers/confidential-containers.git synced 2025-09-18 00:37:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Removing link for now

Browse Source 
Due to some of the discussions in the community, we are removing this
for now.

Signed-off-by: Larry Dewey <larry.dewey@amd.com>
This commit is contained in:
Larry Dewey
2023-04-28 16:52:42 -05:00
committed by Tobin Feldman-Fitzthum
parent c29278b0c7
commit 7ac2cc952a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guides/sev.md
View File

@@ -71,7 +71,7 @@ Usually it should be the public IP of the node where `simple-kbs` runs.
The SEV policy can also be set by adding `io.katacontainers.config.sev.policy: "<SEV POLICY>"` to your pod configuration.
Setting the second bit of the policy enables SEV-ES.
For more information see chapter 3 of the [Secure Encrypted Virtualization API](https://www.amd.com/system/files/TechDocs/55766_SEV-KM_API_Specification.pdf#page=31).
For more information see chapter 3 of the Secure Encrypted Virtualization API.
The SEV policy is not the same as the policies that drive `simple-kbs`.
The CoCo project has created a sample encrypted container image ([encrypted-image-tests](ghcr.io/fitzthum/encrypted-image-tests:encrypted)). This image is encrypted using a key that comes already provisioned inside the `simple-kbs` for ease of testing. No `simple-kbs` policy is required to get things running.