Source repo for Docker's Documentation
Go to file
David Lawrence 12b4b3d80d working on publish with changelist
Signed-off-by: David Lawrence <david.lawrence@docker.com> (github: endophage)
2015-07-09 17:58:09 -07:00
Godeps updating wo make notary work with rufus again 2015-07-09 17:58:09 -07:00
client working on publish with changelist 2015-07-09 17:58:09 -07:00
cmd changelist implementation 2015-07-09 17:58:09 -07:00
errors adding some basic tests for circleci 2015-04-13 15:27:18 -07:00
fixtures rename vetinari to notary 2015-06-19 11:01:19 -07:00
notarymysql fixing trailing comma in mysql 2015-07-05 20:04:21 -07:00
server changelist implementation 2015-07-09 17:58:09 -07:00
signer updating wo make notary work with rufus again 2015-07-09 17:58:09 -07:00
trustmanager changelist implementation 2015-07-09 17:58:09 -07:00
utils adding timestamping and some general cleanup 2015-07-03 15:38:09 -07:00
version rename vetinari to notary 2015-06-19 11:01:19 -07:00
.gitignore adding timestamping and some general cleanup 2015-07-03 15:38:09 -07:00
CONTRIBUTING.md Update contributing for notary 2015-06-21 12:51:35 -07:00
Dockerfile rename vetinari to notary 2015-06-19 11:01:19 -07:00
LICENSE adding apache license 2015-06-20 19:53:49 -07:00
MAINTAINERS adding MAINTAINERS and CONTRIBUTING.md (copied dfrom distribution with a few tweaks) 2015-06-19 13:44:00 -07:00
Makefile rename vetinari to notary 2015-06-19 11:01:19 -07:00
README.md putting the same warning at the top of all the readmes. 2015-06-21 16:13:16 -07:00
ROADMAP.md update readme files for rename 2015-06-19 11:26:52 -07:00
ca.crt Adding new certs to vetinari 2015-04-27 18:39:31 -07:00
circle.yml upgrading stable go to 1.4.2 2015-04-24 11:43:55 -07:00
docker-compose.yml rename vetinari to notary 2015-06-19 11:01:19 -07:00

README.md

Notary is still a work in progress and we invite contributions and reviews from the security community. It will need to go through a formal security review process before it should be used in production.

Notary

Overview

The Notary project comprises a server and a client for running and interacting with trusted collections. Please see the READMEs for the individual tools for more information on their specifics.

Goals

Notary aims to make the internet more secure by making it easy for people to publish and verify content. We often rely on TLS to secure our communications with a web server which is inherently flawed, as any compromise of the server enables malicious content to be substituted for the legitimate content.

With Notary, publishers can sign their content offline using keys kept highly secure. Once the publisher is ready to make the content available, they can push their signed trusted collection to a Notary Server.

Consumers, having acquired the publisher's public key through a secure channel, can then communicate with any notary server or (insecure) mirror, relying only on the publisher's key to determine the validity and integrity of the received content.