From: "David Nyström" <david.nystrom@enea.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] gnutls fixes for master
Date: Wed, 5 Mar 2014 13:34:41 +0100 [thread overview]
Message-ID: <531719E1.2080501@enea.com> (raw)
In-Reply-To: <cover.1394018657.git.paul.eggleton@linux.intel.com>
On 2014-03-05 12:25, Paul Eggleton wrote:
> Turns out we're using the same old version of gnutls in master as in
> dylan and dora, and we need a fix for a compile failure.
>
>
> The following changes since commit 82c773e88aaefd9321481ad297554d5b4a3ae0b2:
>
> Revert "ncurses: use ln -r to generate relative symlink" (2014-03-03 15:52:26 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib paule/gnutls
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/gnutls
>
> Karl Hiramoto (2):
> gnutls: CVE-2014-0092 correct return codes
> gnutls: Fixed bug that prevented the rejection of v1 intermediate CA
> certificates.
>
> Paul Eggleton (1):
> gnutls: fix failure during do_compile
Any specific reasons why we still have the old gnuTLS-2.12.23 ?
Br,
David
next prev parent reply other threads:[~2014-03-05 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 11:25 [PATCH 0/3] gnutls fixes for master Paul Eggleton
2014-03-05 11:25 ` [PATCH 1/3] gnutls: CVE-2014-0092 correct return codes Paul Eggleton
2014-03-05 11:25 ` [PATCH 2/3] gnutls: Fixed bug that prevented the rejection of v1 intermediate CA certificates Paul Eggleton
2014-03-05 11:25 ` [PATCH 3/3] gnutls: fix failure during do_compile Paul Eggleton
2014-03-05 12:34 ` David Nyström [this message]
2014-03-05 13:24 ` [PATCH 0/3] gnutls fixes for master Paul Eggleton
2014-03-05 14:18 ` Valentin Popa
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=531719E1.2080501@enea.com \
--to=david.nystrom@enea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox