Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3] openssl: three CVE patches
Date: Wed, 26 Mar 2014 17:08:42 +0800	[thread overview]
Message-ID: <cover.1395823715.git.jackie.huang@windriver.com> (raw)

From: Jackie Huang <jackie.huang@windriver.com>

The following changes since commit 43d717df16312a8f0333aff6b8b037b4b9d51bf3:

  toaster.bbclass: update buildstats event data (2014-03-25 14:19:57 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib jhuang0/r_port60_openssl_140326-1
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jhuang0/r_port60_openssl_140326-1

Yue Tao (3):
  Security Advisory - openssl - CVE-2013-4353
  Security Advisory - openssl - CVE-2013-6450
  Security Advisory - openssl - CVE-2013-6449

 ...DTLS-retransmission-from-previous-session.patch |   81 ++++++++++++++++++++
 ...or-TLS-record-tampering-bug-CVE-2013-4353.patch |   31 ++++++++
 ...e-version-in-SSL_METHOD-not-SSL-structure.patch |   33 ++++++++
 .../recipes-connectivity/openssl/openssl_1.0.1e.bb |    3 +
 4 files changed, 148 insertions(+)
 create mode 100644 meta/recipes-connectivity/openssl/openssl-1.0.1e/0001-Fix-DTLS-retransmission-from-previous-session.patch
 create mode 100644 meta/recipes-connectivity/openssl/openssl-1.0.1e/0001-Fix-for-TLS-record-tampering-bug-CVE-2013-4353.patch
 create mode 100644 meta/recipes-connectivity/openssl/openssl-1.0.1e/0001-Use-version-in-SSL_METHOD-not-SSL-structure.patch

-- 
1.7.9.5



             reply	other threads:[~2014-03-26  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  9:08 jackie.huang [this message]
2014-03-26  9:08 ` [PATCH 1/3] Security Advisory - openssl - CVE-2013-4353 jackie.huang
2014-03-26  9:08 ` [PATCH 2/3] Security Advisory - openssl - CVE-2013-6450 jackie.huang
2014-03-26  9:08 ` [PATCH 3/3] Security Advisory - openssl - CVE-2013-6449 jackie.huang

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=cover.1395823715.git.jackie.huang@windriver.com \
    --to=jackie.huang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox