- c: Docker Content Trust is based on The Update Framework (TUF) and this framework was created to ensure the release of content between updates using different keys. It is possible to validate the trustfulness of a package or any other content using TUF.
- a and d: Docker Content Trust will use Root, Targets, Snapshot, and Timestamp keys to ensure content.
- c: We ensure image freshness using Content Trust, but it is true that we cannot ensure that the image tagged as "latest" in a given repository is actually the latest one created. We can only ensure that the image tagged as "latest" will be used. It is always recommended to use tags avoiding the use of "latest".
- b: We tried to sign a version of a non-public write repository. We are not allowed to modify root repositories at docker.io.
- d: We can recover the key if we have a backup. If it is not possible, we can generate a new one or let Docker generate one for us on first signing. Although we will...
United States
Great Britain
India
Germany
France
Canada
Russia
Spain
Brazil
Australia
Singapore
Hungary
Ukraine
Luxembourg
Estonia
Lithuania
South Korea
Turkey
Switzerland
Colombia
Taiwan
Chile
Norway
Ecuador
Indonesia
New Zealand
Cyprus
Denmark
Finland
Poland
Malta
Czechia
Austria
Sweden
Italy
Egypt
Belgium
Portugal
Slovenia
Ireland
Romania
Greece
Argentina
Netherlands
Bulgaria
Latvia
South Africa
Malaysia
Japan
Slovakia
Philippines
Mexico
Thailand