You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| root key | Root of content trust for a image tag. When content trust is enabled, you create the root key once. |
117
-
| target and snapshot | These two keys are known together as the "repository" key. When content trust is enabled, you create this key when you add a new image repository. If you have the root key, you can export the repository key and allow other publishers to sign the image tags. |
118
-
| timestamp | This key applies to a repository. It allows Docker repositories to have freshness security guarantees without requiring periodic content refreshes on the client's side. |
119
-
120
-
With the exception of the timestamp, all the keys are generated and stored locally
121
-
client-side. The timestamp is safely generated and stored in a signing server that
122
-
is deployed alongside the Docker registry. All keys are generated in a backend
123
-
service that isn't directly exposed to the internet and are encrypted at rest.
114
+
- an offline key that is the root of content trust for a image tag
115
+
- repository or tagging keys that sign tags
116
+
- server-managed keys such as the timestamp key, which provides freshness
117
+
security guarantees for your repository
124
118
125
119
The following image depicts the various signing keys and their relationships:
126
120
@@ -133,9 +127,9 @@ The following image depicts the various signing keys and their relationships:
133
127
>tag from this repository prior to the loss.
134
128
135
129
You should backup the root key somewhere safe. Given that it is only required
136
-
to create new repositories, it is a good idea to store it offline. Make sure you
137
-
read [Manage keys for content trust](trust_key_mng.md) information
138
-
for details on securing, and backing up your keys.
130
+
to create new repositories, it is a good idea to store it offline.
131
+
For details on securing, and backing up your keys, make sure you
132
+
read how to [manage keys for content trust](trust_key_mng.md).
0 commit comments