Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/7] webkitgtk: update to 2.10.7
Date: Wed, 24 Feb 2016 09:19:27 -0800	[thread overview]
Message-ID: <56CDE61F.7020808@gmail.com> (raw)
In-Reply-To: <56CD9A1F.2060101@linux.intel.com>



On 02/24/2016 03:55 AM, Alexander Kanavin wrote:
> On 02/16/2016 05:55 PM, akuster808 wrote:
> 
>>> Yes, which means that jethro (which has 2.8.5) needs the same update.
>>
>> there is a bug open for that 8877. there are a huge number of CVE's that
>> need fixing.
> 
> I wrote a comment in that bug, but I think it bears repeating here:
> 
> Please read this, it's a bit long, but worth it:
> 
> https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
> 
> Summary: the upstream will not backport CVE fixes, and they will not be
> making point releases in old branches with any kind of lifecycle
> guarantee. Providing ongoing updates to the latest stable release of
> webkit is the only way to stay secure.
> 

Many vulnerability notifications will make the same statements.

Updating a package that other packages depend on can cause a cascading
set of failures. Now you have a bigger set of problems to contend with.

> So I believe that you indeed have to update webkit to 2.10.7, or
> whatever is the latest stable release, and keep doing this for as long
> as a yocto release needs to be supported.

From the commercial side you just can't move your install base to the
latest package versions for every security issue. The Yocto maintenance
policy operates very close to this too.

Yeah, Backporting fixes to stable branches is a lot of work once it
moves away from a simple cherry-pick from master.


regards,
- armin

> 
> Regards,
> Alex
> 


  reply	other threads:[~2016-02-24 17:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 12:42 [PATCH 0/7] Version updates Alexander Kanavin
2016-02-10 12:42 ` [PATCH 1/7] ffmpeg: update to 2.8.6 Alexander Kanavin
2016-02-11 19:05   ` akuster808
2016-02-24  1:55   ` Martin Jansa
2016-02-24 12:34     ` Alexander Kanavin
2016-02-24 13:16       ` Martin Jansa
2016-02-24 13:28         ` Alexander Kanavin
2016-02-24 13:51           ` Martin Jansa
2016-02-10 12:42 ` [PATCH 2/7] gstreamer1.0: fix upstream check for unstable versions from git Alexander Kanavin
2016-02-10 12:42 ` [PATCH 3/7] bash-completion: fix upstream version check Alexander Kanavin
2016-02-10 12:42 ` [PATCH 4/7] iso-codes: update to 3.65 Alexander Kanavin
2016-02-10 12:42 ` [PATCH 5/7] libwnck3: update to 3.14.1 Alexander Kanavin
2016-02-10 12:42 ` [PATCH 6/7] webkitgtk: update to 2.10.7 Alexander Kanavin
2016-02-11 19:08   ` akuster808
2016-02-16 14:34     ` Alexander Kanavin
2016-02-16 15:55       ` akuster808
2016-02-24 11:55         ` Alexander Kanavin
2016-02-24 17:19           ` akuster808 [this message]
2016-02-25 13:55             ` Alexander Kanavin
2016-02-10 12:42 ` [PATCH 7/7] pixz: fix upstream version check Alexander Kanavin

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=56CDE61F.7020808@gmail.com \
    --to=akuster808@gmail.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