From 5e680d54e9e8b849b90047d2d87bc7664edaaa1d Mon Sep 17 00:00:00 2001 From: Lokesh Mandvekar Date: Tue, 12 Apr 2022 09:29:36 -0400 Subject: Bump golang.org/x/crypto to 7b82a4e Resolves: GHSA-8c26-wmh5-6g9v - CVE-2022-27191 Podman doesn't seem to be directly affected as the logic in question is not called. golang.org/x/crypto@1baeb1ce contains the actual CVE fix. Using the latest upstream commit to also include support for SHA-2. Signed-off-by: Lokesh Mandvekar --- vendor/golang.org/x/crypto/pbkdf2/pbkdf2.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'vendor/golang.org/x/crypto/pbkdf2/pbkdf2.go') diff --git a/vendor/golang.org/x/crypto/pbkdf2/pbkdf2.go b/vendor/golang.org/x/crypto/pbkdf2/pbkdf2.go index 593f65300..904b57e01 100644 --- a/vendor/golang.org/x/crypto/pbkdf2/pbkdf2.go +++ b/vendor/golang.org/x/crypto/pbkdf2/pbkdf2.go @@ -32,7 +32,7 @@ import ( // can get a derived key for e.g. AES-256 (which needs a 32-byte key) by // doing: // -// dk := pbkdf2.Key([]byte("some password"), salt, 4096, 32, sha1.New) +// dk := pbkdf2.Key([]byte("some password"), salt, 4096, 32, sha1.New) // // Remember to get a good random salt. At least 8 bytes is recommended by the // RFC. -- cgit v1.2.3-54-g00ecf