From: Terry Barnaby <terry@beam.ltd.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [Openembedded-users] Problem with patch version 2.6.1-7 and after
Date: Thu, 17 Mar 2011 14:32:21 +0000 [thread overview]
Message-ID: <4D821B75.6090206@beam.ltd.uk> (raw)
In-Reply-To: <4D81161E.5090202@mentor.com>
On 03/16/2011 07:57 PM, Tom Rini wrote:
> On 03/16/2011 10:08 AM, Tom Rini wrote:
>> On 03/16/2011 07:03 AM, Terry Barnaby wrote:
>>
>> [snip]
>>> Hi,
>>>
>>> ### Forwarded to openembedded-devel ###
>>>
>>> We are using Fedora14. That is using patch 2.6.1-8.
>>>
>>> The -8 release includes the following patches to patch.
>>> Patch1: patch-2.5.4-sigsegv.patch
>>> Patch2: patch-get-arg.patch
>>> Patch3: patch-CVE-2010-4651.patch
>>> Patch100: patch-selinux.patch
>>>
>>> I think one of those fixes a security issue in patch where ".." in
>>> path names were allowed. With this version of patch (which I assume
>>> will become standard ?) the OpenEmbedded fails.
>>> Any ideas on a way to get around this (ideally without using a
>>> different patch version :) )
>>
>> So, there's a lot of recipes with patches with .. in the path:
>> openembedded$ git grep -lE "^---.*[^.]\.\.\/" recipes/ | wc -l
>> 80
>>
>> Some of these will be easy fixups (first one I peeked at we can just
>> change the patch and not have to modify the recipe) but others like the
>> tcl one will require a little thought.
>
> Everything should be happy now.
>
Indeed it is :)
Thanks very much, I wasn't expecting changes that quick !
Cheers
Terry
prev parent reply other threads:[~2011-03-17 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D80653A.7010804@beam.ltd.uk>
[not found] ` <4D80772A.8080207@atmel.com>
2011-03-16 14:03 ` [Openembedded-users] Problem with patch version 2.6.1-7 and after Terry Barnaby
2011-03-16 17:08 ` Tom Rini
2011-03-16 19:57 ` Tom Rini
2011-03-17 14:32 ` Terry Barnaby [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=4D821B75.6090206@beam.ltd.uk \
--to=terry@beam.ltd.uk \
--cc=openembedded-devel@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