docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update readme files for rename 

Signed-off-by: Nathan McCauley <nathan.mccauley@docker.com>
This commit is contained in:
Nathan McCauley 2015-06-19 11:26:52 -07:00
parent 518d0a2702
commit 84f2754c6d
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -2,9 +2,9 @@
## Overview ## Overview
Notary manages trust metadata as a complementary service to the registry. Notary Server manages trust metadata as a complementary service to the registry.
It implements all endpoints under the `_trust` segment of the registry URLs. It implements all endpoints under the `_trust` segment of the registry URLs.
Notary expects to manage TUF metadata and will do validation of one parent Notary Server expects to manage TUF metadata and will do validation of one parent
level of content for any data uploaded to ensure repositories do not become level of content for any data uploaded to ensure repositories do not become
corrupted. This means either the keys in the root.json file will be used to corrupted. This means either the keys in the root.json file will be used to
validate the uploaded role, or the keys in the immediate delegate parent will validate the uploaded role, or the keys in the immediate delegate parent will
@ -17,16 +17,16 @@ will be sufficient to permit the uploading of a new root.json.
## Timestamping ## Timestamping
TUF requires a timestamp file be regularly generated. To achieve any ease TUF requires a timestamp file be regularly generated. To achieve any ease
of use, it is necessary that Notary is responsible for generating the of use, it is necessary that Notary Server is responsible for generating the
timestamp.json based on the snapshot.json created and uploaded by the timestamp.json based on the snapshot.json created and uploaded by the
repository owner. repository owner.
It is bad policy to place any signing keys in frontline servers. While It is bad policy to place any signing keys in frontline servers. While
Notary is capable of supporting this behaviour we recommend using a Notary Server is capable of supporting this behaviour we recommend using a
separate service and server with highly restricted permissions. Rufus separate service and server with highly restricted permissions. Rufus
is provided as a reference implementation of a remote signer. An is provided as a reference implementation of a remote signer. An
implementation that satisfies the gRPC interface defined in Rufus will implementation that satisfies the gRPC interface defined in Rufus will
satisfy Notary's requirements. satisfy Notary Server's requirements.
# Running # Running

2
ROADMAP.md
View File

@ -1,6 +1,6 @@
# Roadmap # Roadmap
The Trust project consists of a number of moving parts of which Notary is one. Notary is the front line metadata service The Trust project consists of a number of moving parts of which Notary Server is one. Notary Server is the front line metadata service
that clients interact with. It manages TUF metadata and interacts with a pluggable signing service to issue new TUF timestamp that clients interact with. It manages TUF metadata and interacts with a pluggable signing service to issue new TUF timestamp
files. files.