From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [daisy][PATCH] squashfs-tools: enable building unsquashfs and fix squashfs-4.2-fix-CVE-2012-4025.patch
Date: Wed, 1 Jul 2015 15:23:56 +0200 [thread overview]
Message-ID: <20150701132356.GJ2409@jama> (raw)
In-Reply-To: <1432207395-31589-1-git-send-email-Martin.Jansa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
On Thu, May 21, 2015 at 01:23:15PM +0200, Martin Jansa wrote:
> * build unsqaushfs, useful when debuging corrupt squashfs from
> mksquashfs
> * squashfs-4.2-fix-CVE-2012-4025.patch fixes CVE in unsquashfs which we
> weren't building and it actually breaks building it, because someone
> missed squashfs_fs.h change from the original change
> * add git headers in all patches and fix references to new github
> repository
Ping
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-07-01 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 11:23 [daisy][PATCH] squashfs-tools: enable building unsquashfs and fix squashfs-4.2-fix-CVE-2012-4025.patch Martin Jansa
2015-07-01 13:23 ` Martin Jansa [this message]
2015-07-16 14:20 ` Martin Jansa
2015-07-16 19:47 ` Richard Purdie
2015-07-16 20:14 ` Martin Jansa
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=20150701132356.GJ2409@jama \
--to=martin.jansa@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