<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 15 November 2016 at 19:43, T.O. Radzy Radzykewycz <span dir="ltr">&lt;<a href="mailto:radzy@windriver.com" target="_blank">radzy@windriver.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id="gmail-:1ee" class="gmail-a3s gmail-aXjCH gmail-m158698833ac301c0"> .../recipes-connectivity/<wbr>openssl/<a href="http://openssl_1.0.2h.bb" rel="noreferrer" target="_blank">openssl_1.0.2h.bb</a> |  1 +<br></div></blockquote><div><br></div><div>oe-core master is on openssl 1.0.2j now, so please rebase.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id="gmail-:1ee" class="gmail-a3s gmail-aXjCH gmail-m158698833ac301c0">
 2 files changed, 60 insertions(+)<br>
 create mode 100644 meta/recipes-connectivity/<wbr>openssl/openssl/Use-SHA256-<wbr>not-MD5-as-default-digest.<wbr>patch<br>
<br>
diff --git a/meta/recipes-connectivity/<wbr>openssl/openssl/Use-SHA256-<wbr>not-MD5-as-default-digest.<wbr>patch b/meta/recipes-connectivity/<wbr>openssl/openssl/Use-SHA256-<wbr>not-MD5-as-default-digest.<wbr>patch<br>
new file mode 100644<br>
index 000000000000..766af67e1db9<br>
--- /dev/null<br>
+++ b/meta/recipes-connectivity/<wbr>openssl/openssl/Use-SHA256-<wbr>not-MD5-as-default-digest.<wbr>patch<br>
@@ -0,0 +1,59 @@<br>
+From d795f5f20a29adecf92c09459a3ee0<wbr>7ffac01a99 Mon Sep 17 00:00:00 2001<br>
+From: Rich Salz &lt;<a href="mailto:rsalz@akamai.com">rsalz@akamai.com</a>&gt;<br>
+Date: Sat, 13 Jun 2015 17:03:39 -0400<br>
+Subject: [PATCH] Use SHA256 not MD5 as default digest.<br>
+<br>
+Commit f8547f62c212837dbf44fb7e2755e5<wbr>774a59a57b upstream.<br>
+<br>
+Upstream Status: Backport<br></div></blockquote><div><br></div><div>I&#39;m such a pedant but we do have automated tooling around this, so please use &quot;Upstream-Status&quot;.  Also adding a CVE tag in the patch (CVE: CVE-2004-2761) would be appreciated for tracking.</div><div><br></div><div>Ross</div></div></div></div>