Source repo for Docker's Documentation
Go to file
Nathan McCauley 79af8434d3 exclude proto gen'd code from go fmt during circle ci
Signed-off-by: Nathan McCauley <nathan.mccauley@docker.com>
2015-07-14 14:21:52 -07:00
Godeps Godeps update, removed dependency on rufus 2015-07-14 00:39:03 -07:00
client Removing commented out code 2015-07-13 20:32:51 -07:00
cmd Godeps update, removed dependency on rufus 2015-07-14 00:39:03 -07:00
errors adding some basic tests for circleci 2015-04-13 15:27:18 -07:00
fixtures Initial copy of notary-signer 2015-07-14 00:23:22 -07:00
notarymysql refactoring database schema out into its own file for easier use outside of containers 2015-07-13 14:41:51 -07:00
proto Refactored Rufus API 2015-07-14 00:23:38 -07:00
server adding errors if role is empty or bad 2015-07-13 19:50:09 -07:00
signer Add documentation for FindKeyByID function 2015-07-14 14:06:52 -07:00
trustmanager Refactor crypto service 2015-07-13 13:53:47 -07:00
utils Fix access controller resource type 2015-07-13 16:22:05 -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 cleanup dockerfile 2015-07-09 14:43:16 -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 exclude proto gen'd code from go fmt 2015-07-14 14:13: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 Refactored Rufus API 2015-07-14 00:23:38 -07:00
ca.crt Adding new certs to vetinari 2015-04-27 18:39:31 -07:00
circle.yml exclude proto gen'd code from go fmt during circle ci 2015-07-14 14:21:52 -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.