All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Andrej Valek <andrej.valek@siemens.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	Steve Sakoman <steve@sakoman.com>
Subject: Re: [OE-core][PATCH v2] expat: upgrade 2.3.0 -> 2.4.1
Date: Tue, 25 May 2021 23:17:04 +0100	[thread overview]
Message-ID: <8de2b83c408696703284e7204da5285c0b594a47.camel@linuxfoundation.org> (raw)
In-Reply-To: <DB8PR10MB397786AA74112101B3D9845192259@DB8PR10MB3977.EURPRD10.PROD.OUTLOOK.COM>

On Tue, 2021-05-25 at 12:50 +0000, Andrej Valek wrote:
> Hello everyone,
> 
> I have an another question regarding to backporting this to dunfell branch. 
> Is it possible to apply this upgrade to this branch? I would like to have 
> an very important fix for CVE-2013-0340 (https://github.com/libexpat/libexpat/pull/220) 
> there. But there is a lot of changes, means just applying the patch is not very promising.
> 
> How we can handle it?

Adding Steve to Cc. It is possible if there is a good case for it and there
aren't bad side effects from the change. I don't know enough about expat here
to comment on that.

I suspect we should be adding something to the expat recipe to make it match 
libexpat CVEs, maybe CVE_PRODUCT = "libexpat"?

Cheers,

Richard



  reply	other threads:[~2021-05-25 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  9:09 [OE-core][PATCH] expat: upgrade 2.2.10 -> 2.4.1 Andrej Valek
2021-05-25 10:03 ` Alexander Kanavin
2021-05-25 10:13 ` [OE-core][PATCH v2] expat: upgrade 2.3.0 " Andrej Valek
     [not found] ` <168247B8E1E1063C.25934@lists.openembedded.org>
2021-05-25 12:50   ` Andrej Valek
2021-05-25 22:17     ` Richard Purdie [this message]
2021-05-25 22:23       ` Steve Sakoman
2021-05-26  6:24         ` Andrej Valek
2021-05-26 15:02           ` Steve Sakoman
2021-05-25 22:18     ` Steve Sakoman

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=8de2b83c408696703284e7204da5285c0b594a47.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=andrej.valek@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.