distribution/registry/client
Stephen J Day 76624704c3 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
..
auth Make the registry client more tolerant about HTTP status codes 2015-07-24 16:14:04 -07:00
transport Make the registry client more tolerant about HTTP status codes 2015-07-24 16:14:04 -07:00
blob_writer.go Add pull through cache functionality to the Registry which can be configured 2015-08-04 16:09:55 -07:00
blob_writer_test.go Add ability to pass in substitution args into an Error 2015-07-15 11:02:10 -07:00
errors.go Move common error codes to errcode package 2015-08-11 11:50:58 -07:00
repository.go Update to provide small and clear interfaces 2015-10-09 16:05:49 -07:00
repository_test.go Correct unmarshal order for SignedManifest 2015-10-14 14:37:34 -07:00