5 Commits

Author	SHA1	Message	Date
Sebastiaan van Stijn	716291337b	vendor: golang.org/x/crypto 0c34fe9e7dc2486962ef9867e3edb3503537209f ... full diff: c1f2f97bff...0c34fe9e7d Signed-off-by: Sebastiaan van Stijn <github@gone.nl>	2021-06-21 14:29:28 +02:00
Sebastiaan van Stijn	1c3a97b0ff	vendor golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 ... Signed-off-by: Sebastiaan van Stijn <github@gone.nl>	2020-09-09 14:07:50 +02:00
Sebastiaan van Stijn	37d184fe16	vendor: golang.org/x/crypto 2aa609cf4a9d7d1126360de73b55b6002f9e052a ... full diff: bac4c82f69...2aa609cf4a Signed-off-by: Sebastiaan van Stijn <github@gone.nl>	2020-04-22 17:19:00 +02:00
Sebastiaan van Stijn	27d9aa2d9f	vendor: update golang.org/x/crypto 69ecbb4d6d5dab05e49161c6e77ea40a030884e1 (CVE-2020-7919) ... Includes 69ecbb4d6d (forward-port of 8b5121be2f), which fixes CVE-2020-7919: - 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. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>	2020-01-29 11:25:09 +01:00
Tibor Vass	45ec86b10f	vendor github.com/docker/docker to bcaa613d823 ... Signed-off-by: Tibor Vass <tibor@docker.com>	2019-04-03 20:57:18 +00:00