Stephen J Day 26762a54fe Correct unmarshal order for SignedManifest ... To ensure that we only unmarshal the verified payload into the contained manifest, we first copy the entire incoming buffer into Raw and then unmarshal only the Payload portion of the incoming bytes. If the contents is later verified, the caller can then be sure that the contents of the Manifest fields can be trusted. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2015-10-14 14:37:34 -07:00
..
api	Merge pull request #1035 from aaronlehmann/host-parameter-alternate	2015-10-13 14:03:48 -07:00
auth	Switch tests to import "github.com/docker/distribution/context"	2015-08-20 14:50:12 -07:00
client	Correct unmarshal order for SignedManifest	2015-10-14 14:37:34 -07:00
handlers	Correct unmarshal order for SignedManifest	2015-10-14 14:37:34 -07:00
listener	[Server] Listen and serve on a unix socket	2015-05-11 16:00:14 +03:00
middleware	Add pull through cache functionality to the Registry which can be configured	2015-08-04 16:09:55 -07:00
proxy	Avoid returning nil, nil when fetching a manifest by tag by introducing a new	2015-09-18 16:19:37 -07:00
storage	Update to provide small and clear interfaces	2015-10-09 16:05:49 -07:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
registry.go	Add WithVersion to context and other cleanup	2015-09-14 17:14:31 -07:00