Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] openssl: update 1.0.0b to 1.0.0c
Date: Sun, 26 Dec 2010 19:51:05 -0800	[thread overview]
Message-ID: <4D180D29.9090902@gmail.com> (raw)
In-Reply-To: <1293395783-18235-1-git-send-email-khimov@altell.ru>

On 12/26/2010 12:36 PM, Roman I Khimov wrote:
>   * fixes CVE-2010-4180 and CVE-2010-4252
>   * considered as safe upgrade
>
> Signed-off-by: Roman I Khimov<khimov@altell.ru>

Acked-by: Khem Raj <raj.khem@gmail.com>


> ---
>   .../include/angstrom-2008-preferred-versions.inc   |    4 +-
>   .../include/angstrom-2010-preferred-versions.inc   |    4 +-
>   .../include/kaeilos-2009-preferred-versions.inc    |    4 +-
>   conf/distro/include/preferred-shr-versions.inc     |    4 +-
>   .../openssl/openssl-1.0.0b/configure-targets.patch |   31 --
>   recipes/openssl/openssl-1.0.0b/debian.patch        |  515 --------------------
>   .../engines-install-in-libdir-ssl.patch            |   53 --
>   recipes/openssl/openssl-1.0.0b/libdeps-first.patch |   27 -
>   recipes/openssl/openssl-1.0.0b/oe-ldflags.patch    |   22 -
>   recipes/openssl/openssl-1.0.0b/shared-libs.patch   |   48 --
>   .../openssl/openssl-1.0.0c/configure-targets.patch |   31 ++
>   recipes/openssl/openssl-1.0.0c/debian.patch        |  515 ++++++++++++++++++++
>   .../engines-install-in-libdir-ssl.patch            |   53 ++
>   recipes/openssl/openssl-1.0.0c/libdeps-first.patch |   27 +
>   recipes/openssl/openssl-1.0.0c/oe-ldflags.patch    |   22 +
>   recipes/openssl/openssl-1.0.0c/shared-libs.patch   |   48 ++
>   recipes/openssl/openssl-native_1.0.0b.bb           |   27 -
>   recipes/openssl/openssl-native_1.0.0c.bb           |   27 +
>   recipes/openssl/openssl_1.0.0b.bb                  |   30 --
>   recipes/openssl/openssl_1.0.0c.bb                  |   30 ++
>   20 files changed, 761 insertions(+), 761 deletions(-)
>   delete mode 100644 recipes/openssl/openssl-1.0.0b/configure-targets.patch
>   delete mode 100644 recipes/openssl/openssl-1.0.0b/debian.patch
>   delete mode 100644 recipes/openssl/openssl-1.0.0b/engines-install-in-libdir-ssl.patch
>   delete mode 100644 recipes/openssl/openssl-1.0.0b/libdeps-first.patch
>   delete mode 100644 recipes/openssl/openssl-1.0.0b/oe-ldflags.patch
>   delete mode 100644 recipes/openssl/openssl-1.0.0b/shared-libs.patch
>   create mode 100644 recipes/openssl/openssl-1.0.0c/configure-targets.patch
>   create mode 100644 recipes/openssl/openssl-1.0.0c/debian.patch
>   create mode 100644 recipes/openssl/openssl-1.0.0c/engines-install-in-libdir-ssl.patch
>   create mode 100644 recipes/openssl/openssl-1.0.0c/libdeps-first.patch
>   create mode 100644 recipes/openssl/openssl-1.0.0c/oe-ldflags.patch
>   create mode 100644 recipes/openssl/openssl-1.0.0c/shared-libs.patch
>   delete mode 100644 recipes/openssl/openssl-native_1.0.0b.bb
>   create mode 100644 recipes/openssl/openssl-native_1.0.0c.bb
>   delete mode 100644 recipes/openssl/openssl_1.0.0b.bb
>   create mode 100644 recipes/openssl/openssl_1.0.0c.bb
>



      reply	other threads:[~2010-12-27  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-26 20:36 [PATCH] openssl: update 1.0.0b to 1.0.0c Roman I Khimov
2010-12-27  3:51 ` Khem Raj [this message]

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=4D180D29.9090902@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox