Source repo for Docker's Documentation
Go to file
Jessica Frazelle 9f2e3e3d0f pass ldflags to the notary-signer and notary-server builds
in the dockerfiles

Signed-off-by: Jessica Frazelle <acidburn@docker.com>
2015-07-31 09:57:07 -07:00
Godeps Merge pull request #157 from docker/configurable_key_algo 2015-07-30 13:36:01 -07:00
client make key algorithm configurable for local development with in memory ed25519 crypto service 2015-07-30 11:53:39 -07:00
cmd Merge pull request #163 from dmcgowan/refactor-keydbstore 2015-07-30 21:13:32 -07:00
cryptoservice better error handling for invalid password 2015-07-22 11:37:54 -07:00
docs Remove restriction this build builds it all 2015-07-28 18:58:31 -07:00
errors make key algorithm configurable for local development with in memory ed25519 crypto service 2015-07-30 11:53:39 -07:00
fixtures Fixed bug in Root Validation and added more test 2015-07-17 14:33:05 -07:00
keystoremanager Fix gofmt 2015-07-28 18:25:37 -07:00
notarymysql update initial.sql to make schema consistent with staging/prod 2015-07-30 11:17:27 -07:00
pkg/passphrase Avoid printing "Passphrases do not match" when passphrase is too short 2015-07-28 14:41:27 -07:00
proto Fixing protobufs and signer 2015-07-22 16:51:55 -07:00
server Merge pull request #157 from docker/configurable_key_algo 2015-07-30 13:36:01 -07:00
signer Move key database to signer package 2015-07-30 16:22:47 -07:00
trustmanager Move key database to signer package 2015-07-30 16:22:47 -07:00
utils Use correct regular expression for repository names in HTTP handlers 2015-07-27 14:51:59 -07:00
version Removing default version from version.go 2015-07-28 15:38:24 -07:00
.gitignore make key algorithm configurable for local development with in memory ed25519 crypto service 2015-07-30 11:53:39 -07:00
CONTRIBUTING.md Update contributing for notary 2015-06-21 12:51:35 -07:00
Dockerfile fix 2015-07-28 16:06:09 -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 pass ldflags to the notary-signer and notary-server builds 2015-07-31 09:57:07 -07:00
NOTARY_VERSION Renaming VERSION to NOTARY_VERSION 2015-07-30 11:03:36 -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
circle.yml gofmt across the baord 2015-07-20 11:00:24 -07:00
docker-compose.yml viper config for notary signer 2015-07-27 17:33:11 -07:00
notary-server-Dockerfile pass ldflags to the notary-signer and notary-server builds 2015-07-31 09:57:07 -07:00
notary-signer-Dockerfile pass ldflags to the notary-signer and notary-server builds 2015-07-31 09:57:07 -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.