[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130414060630.GA26988@openwall.com>
Date: Sun, 14 Apr 2013 10:06:30 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Endianity in input files
On Sat, Apr 13, 2013 at 05:31:23PM +0200, magnum wrote:
> I did some testing of *2john programs on big-endian and noticed a problem that might be wide-spread: zip2john produces infiles that can only be cracked with a same-endian build of John. That is, some of the hex fields (integers) are in machine's endianness.
Ouch. I am not surprised, though.
> This is not a huge problem but we might want to fix it (in bleeding?). I think all hex fields should be LE regardless of arch.
I agree.
> OTOH if we change it, we break backwards compatibility on BE archs.
Maybe we need to introduce new/revised $-prefixes for the affected
formats, to indicate that they're now reliably LE. Print a warning for
the old ones.
Alexander
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.
