All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 01/10] openssl: update to 1.0.2e
Date: Wed, 9 Dec 2015 11:52:10 -0800	[thread overview]
Message-ID: <5668866A.7030900@gmail.com> (raw)
In-Reply-To: <80f3d12d7eb901a0deb50508d54bd89192b88a8a.1449671297.git.alexander.kanavin@linux.intel.com>

Can we get the CVE's fix by this update included in the commit?

- armin

On 12/09/2015 06:40 AM, Alexander Kanavin wrote:
> [YOCTO #8765]
> [YOCTO #8758]
> 
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
>  .../openssl/{openssl_1.0.2d.bb => openssl_1.0.2e.bb}                  | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta/recipes-connectivity/openssl/{openssl_1.0.2d.bb => openssl_1.0.2e.bb} (94%)
> 
> diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.2d.bb b/meta/recipes-connectivity/openssl/openssl_1.0.2e.bb
> similarity index 94%
> rename from meta/recipes-connectivity/openssl/openssl_1.0.2d.bb
> rename to meta/recipes-connectivity/openssl/openssl_1.0.2e.bb
> index 249f8c4..e41f46b 100644
> --- a/meta/recipes-connectivity/openssl/openssl_1.0.2d.bb
> +++ b/meta/recipes-connectivity/openssl/openssl_1.0.2e.bb
> @@ -39,8 +39,8 @@ SRC_URI += "file://find.pl;subdir=${BP}/util/ \
>              file://ptest_makefile_deps.patch  \
>             "
>  
> -SRC_URI[md5sum] = "38dd619b2e77cbac69b99f52a053d25a"
> -SRC_URI[sha256sum] = "671c36487785628a703374c652ad2cebea45fa920ae5681515df25d9f2c9a8c8"
> +SRC_URI[md5sum] = "5262bfa25b60ed9de9f28d5d52d77fc5"
> +SRC_URI[sha256sum] = "e23ccafdb75cfcde782da0151731aa2185195ac745eea3846133f2e05c0e0bff"
>  
>  PACKAGES =+ " \
>  	${PN}-engines \
> 


  reply	other threads:[~2015-12-09 19:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 14:40 [PATCH 00/10] Recipe version updates Alexander Kanavin
2015-12-09 14:40 ` [PATCH 01/10] openssl: update to 1.0.2e Alexander Kanavin
2015-12-09 19:52   ` akuster808 [this message]
2015-12-10 10:50     ` Alexander Kanavin
2015-12-10 23:13       ` Paul Eggleton
2015-12-11 12:18         ` Alexander Kanavin
2015-12-14 14:34   ` Otavio Salvador
2015-12-15  0:49     ` Khem Raj
2015-12-09 14:40 ` [PATCH 02/10] gnutls: update to 3.4.7 Alexander Kanavin
2015-12-10 22:27   ` Burton, Ross
2015-12-09 14:40 ` [PATCH 03/10] python-setuptools: update to 18.7.1 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 04/10] nspr: update to 4.11 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 05/10] mobile-broadband-provider-info: update to current commit Alexander Kanavin
2015-12-09 14:40 ` [PATCH 06/10] puzzles: " Alexander Kanavin
2015-12-09 14:40 ` [PATCH 07/10] mirrors: replace references to archive.apache.org Alexander Kanavin
2015-12-21 22:21   ` Andre McCurdy
2015-12-22 13:22     ` Alexander Kanavin
2015-12-22 19:52       ` Andre McCurdy
2015-12-09 14:40 ` [PATCH 08/10] json-c: add manual upstream version check Alexander Kanavin
2015-12-09 14:40 ` [PATCH 09/10] subversion: update to 1.9.2 Alexander Kanavin
2015-12-09 14:40 ` [PATCH 10/10] slang: update upstream URI to (official) jedsoft.org Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5668866A.7030900@gmail.com \
    --to=akuster808@gmail.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.