Skip to content

Update image_signing_spec.md #1

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.

Sign up for GitHub

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

Open
navidshaikh wants to merge 1 commit into
base: image_signing_spec
Choose a base branch
from
Open

Update image_signing_spec.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sources/reference/api/image_signing_spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ As Docker application packaging becomes mainstream users need to ensure that the
1. **Verify offline:** Data integrity verification may be performed without connection to Internet.
1. **Remote assembly:** Image layers may be safely pulled from multiple issuers when assembling application layers.
1. **Inspect image assembly:** An application may be inspected to determine how it was assembled and who assembled each layer.
1. **Arbitrary metadata support:** Authors or maintainers may add arbirary metadata describing the applicatation to support their unique needs.
1. **Arbitrary metadata support:** Authors or maintainers may add arbitrary metadata describing the applicatation to support their unique needs.
1. **Application certification support:** Provide mechanism for a certifying party to certify applications built by independent software vendors (ISVs).
1. **Apply Chain of trust model:** In the same way that a signed certificate can be traced to a trusted root CA issuer, layer ancestry built on a series of signed and trusted layers can be trusted.
1. **Retain simplicity:** The signing model should be transparent to the end-user and straightforward for the maintainer. Provide tools to dive deep if information is desired. Otherwise, users are able to easily build images and securly pull images without excessive security burdens.
Expand Down