docs/fixtures/compatibility at befd30e9a4e2d3db0fed29f91c396c474ecfd23a - docs

mirror of https://github.com/docker/docs.git synced 2026-11-05 00:14:17 +03:00

Files

Ying Li 785b2527b1 Test import/export of old repo format.

Signed-off-by: Ying Li <ying.li@docker.com>

2015-12-23 11:47:37 -08:00

notary0.1

Add an example of a 0.1 style repository for backwards compatibility tests

2015-12-22 18:00:57 -08:00

README.md

Test import/export of old repo format.

2015-12-23 11:47:37 -08:00

README.md

This directory contains sample repositories from different versions of Notary client (TUF metadata, trust anchor certificates, and private keys), in order to test backwards compatibility (that newer clients can read old-format repositories).

Notary client makes no guarantees of future-compatibility though (that is, repositories produced by newer clients may not be able to be read by old clients.)

Relevant information for repositories:

notary0.1
- GUN: docker.io/notary0.1/samplerepo
- key passwords: "randompass"
- targets:
```
  NAME                                DIGEST                                SIZE (BYTES)
------------------------------------------------------------------------------------------
  v1     454fd6f9e5a71c34902a673f66cc73be5890785b55014afb0eee6cbbe784cca9   243
```
- timestamp.json has been removed - when testing the metadata, we'll have to rotate the timestamp key in order for the server to be able to sign the timestamp. The timestamp.json generated by a new server will be version 1, since as far as it knows this is a new repo. If we kept the timestamp.json with the higher version number, we would not be able to publish.