[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65fda1ea3225912e11aa8733aa2f4c78@smtp.hushmail.com>
Date: Fri, 22 Mar 2013 10:16:23 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Building unstable jumbo failed
On 22 Mar, 2013, at 7:44 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Fri, Mar 22, 2013 at 6:42 AM, <jfoug@....net> wrote:
>> patch appears fine.
>
> Pushed to unstable-jumbo. Thanks!
>
> --
> Dhiru
>
I wasn't done testing my own patch but I had it the same almost down to the letter :-) and yes, it produces the same outfiles from sample pcaps.
FWIW, if I understand things right, representing a file format or network protocol bitfield with a C bitfield is not guaranteed to be portable - the internal representation of the bitfield is undefined. But I can't see anything we can do about that if it's specified like this.
uaf2john had a similar problem with aliasing a bitfield, I fixed this too now. It does not involve swapping so that is hopefully safe.
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
