[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a0a65abf7cf1cf5957404c648762aefa@smtp.hushmail.com>
Date: Fri, 22 Feb 2013 00:57:25 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Minor problem in ODF format
Cool, thanks! That patch also made odf2john.py less stupid (It used to unzip & read all of content.xml for no reason at all) and that was mostly in the blind: /me no habla python. Apparently it ended up well :-)
magnum
On 22 Feb, 2013, at 0:48 , shane Shane <shane@...twareontheside.info> wrote:
> Hey
>
> This file https://github.com/ShaneQful/odf-dictionary-attack/blob/master/TestFiles/TestBlowfish.odt has a content.xml of only 831 bytes. I've just tested the fix and it worked perfectly where before it didn't.
>
> Regards,
> Shane
>
> On Thu, Feb 21, 2013 at 11:24 PM, magnum <john.magnum@...hmail.com> wrote:
> On 21 Feb, 2013, at 21:17 , Milen Rangelov <gat3way@...il.com> wrote:
>
>>
>> So the correct behaviour is to decrypt the actual length when <= 1024, and then SHA1 that same length? Or what?
>>
>> Yes, that is correct.
>>
>
>
> Fixed now, but untested as I can't produce such files. I did test that it still parses and cracks files with >= 1024 bytes of content.xml correctly.
>
> magnum
>
Content of type "text/html" skipped
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.
