From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] mbedtls: security bump to version 2.6.0
Date: Thu, 07 Sep 2017 11:18:53 +0200 [thread overview]
Message-ID: <87mv66dfya.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <4340454882827bf3f55e05edde6241878a072857.1504638326.git.baruch@tkos.co.il> (Baruch Siach's message of "Tue, 5 Sep 2017 22:05:26 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Fixes CVE-2017-14032: authentication bypass.
> https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02
> Add license hash.
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-09-07 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 19:05 [Buildroot] [PATCH 1/2] shairport-sync: fix static link with mbedtls Baruch Siach
2017-09-05 19:05 ` [Buildroot] [PATCH 2/2] mbedtls: security bump to version 2.6.0 Baruch Siach
2017-09-07 9:18 ` Peter Korsgaard [this message]
2017-09-07 13:15 ` Peter Korsgaard
2017-09-05 19:44 ` [Buildroot] [PATCH 1/2] shairport-sync: fix static link with mbedtls Thomas Petazzoni
2017-09-06 5:30 ` Baruch Siach
2017-09-24 11:52 ` Arnout Vandecappelle
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=87mv66dfya.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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