f3a05eb800
Some warnings about go1.16 compatibility, so including them here: + go mod tidy -modfile=vendor.mod github.com/docker/cli/cli/registry/client imports github.com/docker/distribution/registry/api/v2 imports github.com/gorilla/mux loaded from github.com/gorilla/mux@v1.7.0, but go 1.16 would select v1.8.0 github.com/docker/cli/cli/compose/loader imports gopkg.in/yaml.v2 tested by gopkg.in/yaml.v2.test imports gopkg.in/check.v1 loaded from gopkg.in/check.v1@v1.0.0-20200227125254-8fa46927fb4f, but go 1.16 would select v1.0.0-20201130134442-10cb98267c6c github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/Shopify/logrus-bugsnag loaded from github.com/Shopify/logrus-bugsnag@v0.0.0-20170309145241-6dbc35f2c30d, but go 1.16 would select v0.0.0-20171204204709-577dee27f20d github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go/ext loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go/log loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/afero loaded from github.com/spf13/afero@v1.1.2, but go 1.16 would select v1.2.2 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/cast loaded from github.com/spf13/cast@v1.3.0, but go 1.16 would select v1.3.1 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/jwalterweatherman loaded from github.com/spf13/jwalterweatherman@v1.0.0, but go 1.16 would select v1.1.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports gopkg.in/ini.v1 loaded from gopkg.in/ini.v1@v1.51.0, but go 1.16 would select v1.56.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/afero imports github.com/spf13/afero/mem loaded from github.com/spf13/afero@v1.1.2, but go 1.16 would select v1.2.2 To upgrade to the versions selected by go 1.16: go mod tidy -go=1.16 && go mod tidy -go=1.17 If reproducibility with go 1.16 is not needed: go mod tidy -compat=1.17 For other options, see: https://golang.org/doc/modules/pruning Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
---|---|---|
.. | ||
.mailmap | ||
.pullapprove.yml | ||
.travis.yml | ||
CONTRIBUTING.md | ||
LICENSE | ||
LICENSE.docs | ||
MAINTAINERS | ||
README.md | ||
algorithm.go | ||
digest.go | ||
digester.go | ||
doc.go | ||
verifiers.go |
README.md
go-digest
Common digest package used across the container ecosystem.
Please see the godoc for more information.
What is a digest?
A digest is just a hash.
The most common use case for a digest is to create a content identifier for use in Content Addressable Storage systems:
id := digest.FromBytes([]byte("my content"))
In the example above, the id can be used to uniquely identify the byte slice "my content". This allows two disparate applications to agree on a verifiable identifier without having to trust one another.
An identifying digest can be verified, as follows:
if id != digest.FromBytes([]byte("my content")) {
return errors.New("the content has changed!")
}
A Verifier
type can be used to handle cases where an io.Reader
makes more sense:
rd := getContent()
verifier := id.Verifier()
io.Copy(verifier, rd)
if !verifier.Verified() {
return errors.New("the content has changed!")
}
Using Merkle DAGs, this can power a rich, safe, content distribution system.
Usage
While the godoc is considered the best resource, a few important items need to be called out when using this package.
-
Make sure to import the hash implementations into your application or the package will panic. You should have something like the following in the main (or other entrypoint) of your application:
import ( _ "crypto/sha256" _ "crypto/sha512" )
This may seem inconvenient but it allows you replace the hash implementations with others, such as https://github.com/stevvooe/resumable.
-
Even though
digest.Digest
may be assemblable as a string, always verify your input withdigest.Parse
or useDigest.Validate
when accepting untrusted input. While there are measures to avoid common problems, this will ensure you have valid digests in the rest of your application. -
While alternative encodings of hash values (digests) are possible (for example, base64), this package deals exclusively with hex-encoded digests.
Stability
The Go API, at this stage, is considered stable, unless otherwise noted.
As always, before using a package export, read the godoc.
Contributing
This package is considered fairly complete. It has been in production in thousands (millions?) of deployments and is fairly battle-hardened. New additions will be met with skepticism. If you think there is a missing feature, please file a bug clearly describing the problem and the alternatives you tried before submitting a PR.
Code of Conduct
Participation in the OpenContainers community is governed by OpenContainer's Code of Conduct.
Security
If you find an issue, please follow the security protocol to report it.
Copyright and license
Copyright © 2019, 2020 OCI Contributors
Copyright © 2016 Docker, Inc.
All rights reserved, except as follows.
Code is released under the Apache 2.0 license.
This README.md
file and the CONTRIBUTING.md
file are licensed under the Creative Commons Attribution 4.0 International License under the terms and conditions set forth in the file LICENSE.docs
.
You may obtain a duplicate copy of the same license, titled CC BY-SA 4.0, at http://creativecommons.org/licenses/by-sa/4.0/.