[oe-commits] [openembedded-core] branch master-next updated: openssl: actually apply Use-SHA256-not-MD5-as-default-digest.patch

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a commit to branch master-next
in repository openembedded-core.

The following commit(s) were added to refs/heads/master-next by this push:
     new 8791800  openssl: actually apply Use-SHA256-not-MD5-as-default-digest.patch
8791800 is described below

commit 8791800f84321b3f46772bc2d9e4f754e6213946
Author: Ross Burton <ross.burton at intel.com>
AuthorDate: Tue Mar 14 12:49:47 2017 +0000

    openssl: actually apply Use-SHA256-not-MD5-as-default-digest.patch
    
    This patch was added to fix a CVE, but wasn't actually added to SRC_URI:
    
        CVE: CVE-2004-2761
        The MD5 Message-Digest Algorithm is not collision resistant,
        which makes it easier for context-dependent attackers to
        conduct spoofing attacks, as demonstrated by attacks on the
        use of MD5 in the signature algorithm of an X.509 certificate.
    
    Signed-off-by: Ross Burton <ross.burton at intel.com>
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 meta/recipes-connectivity/openssl/openssl_1.0.2k.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.2k.bb b/meta/recipes-connectivity/openssl/openssl_1.0.2k.bb
index 1973f81..922819b 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.0.2k.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.0.2k.bb
@@ -41,6 +41,7 @@ SRC_URI += "file://find.pl;subdir=${BP}/util/ \
             file://configure-musl-target.patch \
             file://parallel.patch \
             file://openssl-util-perlpath.pl-cwd.patch \
+            file://Use-SHA256-not-MD5-as-default-digest.patch \
            "
 SRC_URI[md5sum] = "f965fc0bf01bf882b31314b61391ae65"
 SRC_URI[sha256sum] = "6b3977c61f2aedf0f96367dcfb5c6e578cf37e7b8d913b4ecb6643c3cb88d8c0"

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.