Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Valentin Popa <valentin.popa@intel.com>
To: "Paul Eggleton" <paul.eggleton@linux.intel.com>,
	"David Nyström" <david.nystrom@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] gnutls fixes for master
Date: Wed, 05 Mar 2014 16:18:33 +0200	[thread overview]
Message-ID: <53173239.4000504@intel.com> (raw)
In-Reply-To: <3814042.TXeI6vvODN@peggleto-mobl5.ger.corp.intel.com>

On 03/05/2014 03:24 PM, Paul Eggleton wrote:
> Hi David,
>
> On Wednesday 05 March 2014 13:34:41 David Nyström wrote:
>> 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 ?
> I'm not sure - there's no NO_UPGRADE_REASON set in our inc files to suggest
> why. Googling turned this up:
>
>   https://wiki.debian.org/gnutls3
>
> Valentin, Saul - we probably ought to have NO_UPGRADE_REASON set for gnutls if
> we have a good reason for staying with 2.12.x.
>
> Cheers,
> Paul
>

There is no valid regex for gnutls at the moment. I'll update it. As for 
the recommended version Saul or Ross might  know more.




      reply	other threads:[~2014-03-05 14:18 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 ` [PATCH 0/3] gnutls fixes for master David Nyström
2014-03-05 13:24   ` Paul Eggleton
2014-03-05 14:18     ` Valentin Popa [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=53173239.4000504@intel.com \
    --to=valentin.popa@intel.com \
    --cc=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