Sebastiaan van Stijn b606c8e440 vendor: update golang.org/x/crypto 69ecbb4d6d5dab05e49161c6e77ea40a030884e1 ... full diff: 88737f569e...69ecbb4d6d 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 18:36:06 +01:00
..
internal/rc2	Update miekg/dns to v1.0.7	2018-06-01 16:24:59 +02:00
bmp-string.go	revendor logrus and x/crypto	2017-09-14 11:05:47 -05:00
crypto.go	Update miekg/dns to v1.0.7	2018-06-01 16:24:59 +02:00
errors.go	project: use vndr for vendoring	2016-11-03 15:31:46 -07:00
mac.go	project: use vndr for vendoring	2016-11-03 15:31:46 -07:00
pbkdf.go	project: use vndr for vendoring	2016-11-03 15:31:46 -07:00
pkcs12.go	vendor: update golang.org/x/crypto 69ecbb4d6d5dab05e49161c6e77ea40a030884e1	2020-01-29 18:36:06 +01:00
safebags.go	project: use vndr for vendoring	2016-11-03 15:31:46 -07:00