public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Sona Sarmadi <sona.sarmadi@enea.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: CVE-2016-3116: dropbear: X11 forwarding input not validated properly
Date: Wed, 14 Sep 2016 13:31:26 +0300	[thread overview]
Message-ID: <6d86b220-85ac-f28a-3d7f-824526e7d97a@linux.intel.com> (raw)
In-Reply-To: <3230301C09DEF9499B442BBE162C5E48ABE3BB09@SESTOEX04.enea.se>

On 09/14/2016 01:24 PM, Sona Sarmadi wrote:

> Thanks guys for your feedbacks. I agree that by default we shouldn't upgrade package
> versions in stable branches as far as possible but sometimes we have to. If there isn't a
> suitable patch I personally prefer upgrading (only if it is minor changes) rather than
> sticking to a vulnerable version. We have done this in the past e.g. for OpenSSL (from
> 1.0.1x to 1.0.1y).

See, often the upstream does have a way to get security fixes out to 
users in a way that doesn't bundle unrelated feature additions and 
changes. By saying 'we should trust the upstream' I mean that we should 
try to fix security in a way provided by upstream instead of doing the 
backporting ourselves (where frequently we have no idea what we're 
really doing because we don't know the codebase, or it's otherwise too 
hard for various reasons).

> I will do some investigation to find out if https://secure.ucc.asn.au/hg/dropbear/rev/a3e8389e01ff
> is the fix for CVE-2016-3116 (by quick analysis it looks the right patch) and use that patch and NOT
> upgrade the dropbear version in krogoth !!

After looking at commit tree, I'm pretty certain that it is. And you can 
just update to 2016.72 because it is the only change in that version.

Alex


  reply	other threads:[~2016-09-14 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  8:49 CVE-2016-3116: dropbear: X11 forwarding input not validated properly Sona Sarmadi
2016-09-14  9:06 ` Alexander Kanavin
2016-09-14  9:43   ` Richard Purdie
2016-09-14  9:58     ` Alexander Kanavin
2016-09-14 10:24       ` Sona Sarmadi
2016-09-14 10:31         ` Alexander Kanavin [this message]
2016-09-14 20:19     ` akuster808

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=6d86b220-85ac-f28a-3d7f-824526e7d97a@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sona.sarmadi@enea.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