From: Saul Wold <sgw@linux.intel.com>
To: Qian Lei <qianl.fnst@cn.fujitsu.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH] openssl: upgrade to 1.0.1l
Date: Tue, 27 Jan 2015 20:05:06 -0800 [thread overview]
Message-ID: <54C85FF2.7080408@linux.intel.com> (raw)
In-Reply-To: <1422414850-28982-1-git-send-email-qianl.fnst@cn.fujitsu.com>
I think that 1.0.2 is now released also!
Sau!
On 01/27/2015 07:14 PM, Qian Lei wrote:
>
> | Changes between 1.0.1k and 1.0.1l [15 Jan 2015]
> |
> | *) Build fixes for the Windows and OpenVMS platforms
> | [Matt Caswell and Richard Levitte]
> |
> | Changes between 1.0.1j and 1.0.1k [8 Jan 2015]
> |
> | (CVE-2014-3571)
> | (CVE-2015-0206)
> | (CVE-2014-3569)
> | (CVE-2014-3572)
> | (CVE-2015-0204)
> | (CVE-2015-0205)
> | (CVE-2014-8275)
> | (CVE-2014-3570)
> |
> | *) Ensure that the session ID context of an SSL is updated when its
> | SSL_CTX is updated via SSL_set_SSL_CTX.
> |
> | *) Fix various certificate fingerprint issues.
> |
> | *) Do not resume sessions on the server if the negotiated protocol
> | version does not match the session's version. Resuming with a different
> | version, while not strictly forbidden by the RFC, is of questionable
> | sanity and breaks all known clients.
> | [David Benjamin, Emilia Käsper]
> |
> | *) Tighten handling of the ChangeCipherSpec (CCS) message: reject
> | early CCS messages during renegotiation. (Note that because
> | renegotiation is encrypted, this early CCS was not exploitable.)
> | [Emilia Käsper]
> |
> | *) Tighten client-side session ticket handling during renegotiation:
> | ensure that the client only accepts a session ticket if the server sends
> | the extension anew in the ServerHello. Previously, a TLS client would
> | reuse the old extension state and thus accept a session ticket if one was
> | announced in the initial ServerHello.
> |
> | Similarly, ensure that the client requires a session ticket if one
> | was advertised in the ServerHello. Previously, a TLS client would
> | ignore a missing NewSessionTicket message.
> | [Emilia Käsper]
>
> Signed-off-by: Qian Lei <qianl.fnst@cn.fujitsu.com>
> ---
> .../openssl/{openssl_1.0.1j.bb => openssl_1.0.1l.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-connectivity/openssl/{openssl_1.0.1j.bb => openssl_1.0.1l.bb} (92%)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.1j.bb b/meta/recipes-connectivity/openssl/openssl_1.0.1l.bb
> similarity index 92%
> rename from meta/recipes-connectivity/openssl/openssl_1.0.1j.bb
> rename to meta/recipes-connectivity/openssl/openssl_1.0.1l.bb
> index 2da18ae..840b995 100644
> --- a/meta/recipes-connectivity/openssl/openssl_1.0.1j.bb
> +++ b/meta/recipes-connectivity/openssl/openssl_1.0.1l.bb
> @@ -38,8 +38,8 @@ SRC_URI += "file://configure-targets.patch \
> file://run-ptest \
> "
>
> -SRC_URI[md5sum] = "f7175c9cd3c39bb1907ac8bba9df8ed3"
> -SRC_URI[sha256sum] = "1b60ca8789ba6f03e8ef20da2293b8dc131c39d83814e775069f02d26354edf3"
> +SRC_URI[md5sum] = "cdb22925fc9bc97ccbf1e007661f2aa6"
> +SRC_URI[sha256sum] = "b2cf4d48fe5d49f240c61c9e624193a6f232b5ed0baf010681e725963c40d1d4"
>
> PACKAGES =+ " \
> ${PN}-engines \
>
prev parent reply other threads:[~2015-01-28 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 3:14 [master][PATCH] openssl: upgrade to 1.0.1l Qian Lei
2015-01-28 4:05 ` Saul Wold [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=54C85FF2.7080408@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qianl.fnst@cn.fujitsu.com \
/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.