[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6b75501a595d2f60a06aaf8535ffb99b@smtp.hushmail.com>
Date: Fri, 29 Jun 2012 01:35:09 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: formats failing on big-endian
On 2012-06-28 22:59, Solar Designer wrote:
> On Thu, Jun 28, 2012 at 10:27:30PM +0200, magnum wrote:
>> On 2012-06-28 22:17, Solar Designer wrote:
>>> Benchmarking: MS SQL 2005 SHA-1 [32/32]... FAILED (get_hash[0](0))
>>> Benchmarking: Office 2007/2010 SHA-1/AES [32/32]... FAILED (cmp_all(1))
>>> Benchmarking: RAR3 SHA-1 AES (4 characters) [32/32]... FAILED (cmp_all(1))
>>> 3 out of 113 tests have FAILED
> [...]
>> I think it was mentioned somewhere: These were the few ones not fixed by
>> Jim when he did the Sparc. I have no access to any usable host so I
>> can't do much (the RAR format includes big-endian stuff from
>> dry-running). The MSSQL should be easy but again, I have no gear. For
>> Office, I have no idea. I think we should ignore these and just say they
>> are broken on BE for now.
>
> I am OK with this. Can you create doc/BUGS with this info, please?
Done. It includes the above as well as the problematic CUDA mscash
formats. We have several more GPU formats that needs fixing OR should be
added.
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.
