The toolkit to pack, ship, store, and deliver container content
Find a file
Sebastiaan van Stijn 4ae059c714
Update Golang 1.13.7 (CVE-2020-0601, CVE-2020-7919)
full diff: https://github.com/golang/go/compare/go1.13.4...go1.13.7

go1.13.7 (released 2020/01/28) includes two security fixes. One mitigates
the CVE-2020-0601 certificate verification bypass on Windows. The other affects
only 32-bit architectures.

https://github.com/golang/go/issues?q=milestone%3AGo1.13.7+label%3ACherryPickApproved

- X.509 certificate validation bypass on Windows 10
  A Windows vulnerability allows attackers to spoof valid certificate chains when
  the system root store is in use. These releases include a mitigation for Go
  applications, but it’s strongly recommended that affected users install the
  Windows security update to protect their system.
  This issue is CVE-2020-0601 and Go issue golang.org/issue/36834.
- Panic in crypto/x509 certificate parsing and golang.org/x/crypto/cryptobyte
  On 32-bit architectures, a malformed input to crypto/x509 or the ASN.1 parsing
  functions of golang.org/x/crypto/cryptobyte can lead to a panic.
  The malformed certificate can be delivered via a crypto/tls connection to a
  client, or to a server that accepts client certificates. net/http clients can
  be made to crash by an HTTPS server, while net/http servers that accept client
  certificates will recover the panic and are unaffected.
  Thanks to Project Wycheproof for providing the test cases that led to the
  discovery of this issue. The issue is CVE-2020-7919 and Go issue golang.org/issue/36837.
  This is also fixed in version v0.0.0-20200124225646-8b5121be2f68 of golang.org/x/crypto/cryptobyte.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-02-21 23:45:49 +01:00
cmd Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
configuration Fix gometalint errors 2019-02-04 16:01:04 -08:00
context remove closenotifier 2018-09-11 16:14:10 -07:00
contrib registry: fix binary JSON content-type 2019-01-14 09:04:42 +00:00
digestset Enable static checks 2018-08-06 14:49:11 -07:00
docs Fixing broken table 2019-11-26 17:38:40 -08:00
health Merge pull request #2813 from lucab/ups/spec-json-binary 2019-03-01 14:26:54 -08:00
manifest Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
metrics Add notification metrics 2019-02-15 21:14:57 +08:00
notifications Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
project Adds pre-commit hook, hook config script, and a README 2014-12-15 18:09:11 -08:00
reference Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
registry Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
releases Release notes for 2.7 2018-11-29 16:35:06 -08:00
script Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
testutil Enable static checks 2018-08-06 14:49:11 -07:00
uuid Only enable uuid generation warning when using registry handlers 2015-07-30 14:27:07 -07:00
vendor update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
version Release notes for 2.7 2018-11-29 16:35:06 -08:00
.gitignore add s3 region filters for cloudfront 2017-12-01 15:58:58 -08:00
.golangci.yml Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
.mailmap Update mailmap file 2018-09-26 11:15:01 -07:00
.travis.yml Update Golang 1.13.7 (CVE-2020-0601, CVE-2020-7919) 2020-02-21 23:45:49 +01:00
blobs.go Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
BUILDING.md fix out of date cli arg for registry version 2018-02-28 06:46:06 +08:00
CONTRIBUTING.md Update CONTRIBUTING.md 2017-12-29 14:41:43 +02:00
doc.go fix some typos in source comments 2015-04-17 12:39:52 +00:00
Dockerfile Update Golang 1.13.7 (CVE-2020-0601, CVE-2020-7919) 2020-02-21 23:45:49 +01:00
errors.go disable schema1 by default, add a config flag to enable it 2017-12-19 10:23:25 -08:00
go.mod update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
go.sum update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
LICENSE Initial commit 2014-12-22 15:49:26 -08:00
MAINTAINERS Add new reviewers 2018-08-20 12:24:15 -07:00
Makefile Migrate to golangci-lint 2020-02-14 08:11:16 +11:00
manifests.go Fix gometalint errors 2019-02-04 16:01:04 -08:00
README.md use travis, not circle, build badge 2019-09-04 15:38:24 -07:00
registry.go add support for repo deleted event also 2018-08-02 23:05:05 -07:00
ROADMAP.md fix typos 2016-06-02 23:03:27 +08:00
tags.go Migrate to golangci-lint 2020-02-14 08:11:16 +11:00

Distribution

The Docker toolset to pack, ship, store, and deliver content.

This repository's main product is the Docker Registry 2.0 implementation for storing and distributing Docker images. It supersedes the docker/docker-registry project with a new API design, focused around security and performance.

Build Status GoDoc

This repository contains the following components:

Component Description
registry An implementation of the Docker Registry HTTP API V2 for use with docker 1.6+.
libraries A rich set of libraries for interacting with distribution components. Please see godoc for details. Note: These libraries are unstable.
specifications Distribution related specifications are available in docs/spec
documentation Docker's full documentation set is available at docs.docker.com. This repository contains the subset related just to the registry.

How does this integrate with Docker engine?

This project should provide an implementation to a V2 API for use in the Docker core project. The API should be embeddable and simplify the process of securely pulling and pushing content from docker daemons.

What are the long term goals of the Distribution project?

The Distribution project has the further long term goal of providing a secure tool chain for distributing content. The specifications, APIs and tools should be as useful with Docker as they are without.

Our goal is to design a professional grade and extensible content distribution system that allow users to:

  • Enjoy an efficient, secured and reliable way to store, manage, package and exchange content
  • Hack/roll their own on top of healthy open-source components
  • Implement their own home made solution through good specs, and solid extensions mechanism.

More about Registry 2.0

The new registry implementation provides the following benefits:

  • faster push and pull
  • new, more efficient implementation
  • simplified deployment
  • pluggable storage backend
  • webhook notifications

For information on upcoming functionality, please see ROADMAP.md.

Who needs to deploy a registry?

By default, Docker users pull images from Docker's public registry instance. Installing Docker gives users this ability. Users can also push images to a repository on Docker's public registry, if they have a Docker Hub account.

For some users and even companies, this default behavior is sufficient. For others, it is not.

For example, users with their own software products may want to maintain a registry for private, company images. Also, you may wish to deploy your own image repository for images used to test or in continuous integration. For these use cases and others, deploying your own registry instance may be the better choice.

Migration to Registry 2.0

For those who have previously deployed their own registry based on the Registry 1.0 implementation and wish to deploy a Registry 2.0 while retaining images, data migration is required. A tool to assist with migration efforts has been created. For more information see docker/migrator.

Contribute

Please see CONTRIBUTING.md for details on how to contribute issues, fixes, and patches to this project. If you are contributing code, see the instructions for building a development environment.

Support

If any issues are encountered while using the Distribution project, several avenues are available for support:

IRC #docker-distribution on FreeNode
Issue Tracker github.com/docker/distribution/issues
Google Groups https://groups.google.com/a/dockerproject.org/forum/#!forum/distribution
Mailing List docker@dockerproject.org

License

This project is distributed under Apache License, Version 2.0.